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
--
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
