Joel Becker <Joel.Becker@xxxxxxxxxx> writes: >> Please, no. I understand where you're coming from with this request, but >> think of it from the point of view of non-long-time users (or users who >> have been keeping up with the changelog) who want to look up some piece of >> information. The last thing they want to have to do is read through a bunch >> of irrelevant information related to the behavior of obsolete versions of >> git they've never even used. > > ... In > fact, when you are silently changing existing behavior, it's the people > in between that will get bitten. The new user never knew the old way, > and the git@vger reader already knows. For the record, I am with Joel on this one. That's why we ship reasonably detailed Release Notes that mentions all the notable changes in the release these days, starting from 1.5.0. We probably could do more and/or better, but offhand I do not think of a way to do so without being too verbose in the main manual pages. Having said that, calling anything in the 1.5.0 release "silently changed" _is_ going too far, I think. I think we made a reasonable effort to make it clear certain things are different, while the new tools would work on old repositories. Certain packfile transfer features are only enabled after software version negotiation on both ends, which unfortunately would cause problems if you pull with 1.5.0 or later client and still use older client in the same repository after that, but I do not see much way around that without being too annoying to the more typical users who use a single version of git on a single repository (iow after upgrade, you do not mix, you keep using the new one). - 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
