On Thu, Jan 26, 2012 at 11:15:08AM -0800, Junio C Hamano wrote: > > ... (I notice you mostly include features and not bug-fixes, which I > > assume is to keep the list to a readable length). > > Actually my intention regarding fixes are: > > - never mention follow-up fixes to new topics merged since v1.7.8 at all; > > - omit mentioning trivial fixes that not many people would be bitten by > and actually be hurt in real life (i.e. typo in an error message); and > > - make sure as many fixes are covered in "Fixes since v1.7.8" section. > > So "keep the list short" is only one-third of the motivation. That makes sense. I was specifically thinking of 02f7914 (remote-curl: don't pass back fake refs), because "git push --mirror" failing is an often-reported bug for github (and the solution is to upgrade your git client). But looking again, I see that the fix was actually in v1.7.8.2, so it is included by the "...and all of the fixes in the maintenance releases" text. In general, it seems like most of our fixes go onto the maintenance track, so the "fixes" section of a major release ends up being empty. Which I think is a good thing. -Peff -- 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