Johannes Schindelin <Johannes.Schindelin@gmx.de> writes: >> If you have such a modified rev-list, yes. I was having doubts >> about keeping an obvious correctness guarantee when doing such >> "rev-list ~A". > > I think it would be trivial: just resolve ~A to the tree A points to: <tired> Hmph. I thought you meant "have-only A" to mean similar to "have A" but additionally "do not assume I have things behind A", and are going to extend rev-list to support ~A syntax to do that. I am a bit surprised to see your "rev-list ~A" is to include A, not exclude A and not what are behind A. Where is the connection between this and "have-only A"? </tired> ;-) >> > Yes, I agree. But again, the local repo has to know which grafts were >> > introduced by making the repo shallow. >> >> I am not sure I understand. grafts are grafts are grafts. > > Exactly. And grafts are grafts are not necessarily cutoffs. > > Now, is it possible that a fetch does something unintended, when there are > grafts which are not cutoffs? I don't know yet, but I think so. I think we are disagreeing, so "not Exactly". I meant "grafts are grafts, there is no cutoffs, they are also just grafts". So the answer to your question is "it does not matter". - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Thu Feb 02 12:17:47 2006
This archive was generated by hypermail 2.1.8 : 2006-02-02 12:18:56 EST