Re: [kernel.org users] [RFD] On deprecating "git-foo" for builtins
- From
- Perry Wagle <wagle@cs.indiana.edu>
- Date
- Aug 28, 2008, 23:12 UTC
- Message-ID
- <881C17DA-2FE2-49A7-A4A9-FACA7720599C@cs.indiana.edu>
- In-Reply-To
- <3DE083DB-ADFF-45E7-B3EB-A76985941271@cs.indiana.edu>
Jeff King has convinced me that it's perfectly legitimate to introduce non-upward compatibilities in minor version releases of "young" software.
My introduction to the problem was Tuesday of this week and this thread. The reasoning that I generally saw in this thread was insane, and it scared me. With some of the feedback I received, I now see a bigger picture where these decisions aren't so willy-nilly.
I think the lesson here, however, it that the correct way to have done this is to first remove all the git<DASH>'s from the source, demos, sample, documentation, etc. Second, BIG PAUSE (full minor version release cycle?) Then, third, get rid of git<DASH> in <prefix>/bin.
The doctor expects my full recovery tomorrow. 8)
Thanks!
-- Perry