On Wed, Feb 03, 2010 at 08:01:17PM +0100, demerphq wrote: > Shouldn't an old git just ignore headers from a new git? > > I mean, forget about the fact that somebody is doing something naughty > with the git protocol, ask youself if you want this rule to basically > prevent any backwards compatible changes with older gits. We have done similar changes in the past and if there would be such a change, we can phase-in it over the course of several releases. I think the fall-out would not be that bad; we have some experience with even making Debian-stable Git compatible with new stuff. ;-) Also, what if any extra header would be essential and we _wanted_ non-compatible Git to break down on it? On the other hand, allowing this preventively would apparently have the immediate effect of alternative implementations users happily starting to use it, and then to get to the data, people would demand git-core support as well. _And_ so far everyone seems really really fairly sure we don't want the headers and it's not likely to change. P.S.: On the other hand, I think that change was probably just misguided, not malicious. And I wouldn't be that hard on Dulwich, it's an early-0.x software after all, it's allowed to crash and have protocol issues. ;-) -- Petr "Pasky" Baudis If you can't see the value in jet powered ants you should turn in your nerd card. -- Dunbal (464142) -- 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