On Wed, Nov 21, 2012 at 5:17 AM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > Junio C Hamano wrote: >> Felipe Contreras <felipe.contreras@xxxxxxxxx> writes: > >>> Of course, transport-helper shouldn't even be specifying the negative >>> (^) refs, but that's another story. >> >> Hrm, I am not sure I understand what you mean by this. >> >> How should it be telling the fast-export up to what commit the >> receiving end should already have the history for (hence they do not >> need to be sent)? Or are you advocating to re-send the entire >> history down to the root commit every time? > > I think Felipe has mentioned before that he considers it the remote > helper's responsibility to keep track of what commits have already > been imported, for example using a marks file. It's not the remote helper, fast-export does that. > Never mind that others have said that that's not the current interface > (I don't yet see why it would be a good interface after a transition, > but maybe it would be). Still, hopefully that clarifies the intended > meaning. The current interface is broken. not ok 16 - pulling without marks # TODO known breakage not ok 17 - pushing without marks # TODO known breakage See? A remote helper without marks doesn't work. -- Felipe Contreras -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html