On Fri, Jul 3, 2015 at 7:10 PM, Andrew Savchenko <birc...@gentoo.org> wrote: > > We have a rule of "one year compatibility period". ChangeLog shows > that git-2.2.0 was introduced on 02 Dec 2014. So pushed commits > can't be enforced before 02 Dec 2015. (And yes, my laptop > still uses an older version, that's why I was unable to find --sign > in the git-push manual.) >
In general we try to avoid breaking the upgrade path for user systems that only upgrade annually, but no such limitation applies to developers. I don't think it is too much to expect a developer to use a recent version of git. Users don't need git push signing support to use Gentoo. By all means debate the importance of the feature/etc, but I don't see a need to freeze any new git feature for a year before making use of it with the gentoo repository. If it really bothers you, do your pushes from a chroot. It isn't like I close any gcc-5 bugs with "can't be bothered to look at gcc-5 - give me a call in a year or two." -- Rich
