Quoting Junio C Hamano <gitster@xxxxxxxxx>: > By the way, how are you researching these old discussions? Do you have > a huge list of bookmarks? There weren't that many threads that became the turning points for the project; the list need not to be huge even if somebody were to keep one. But I don't keep such a list; I just ask the gmane archive or google. > And the most scary part of all is that you cannot try both. We now know > that for 1.6.0 transition people _claimed_ that they would have liked > louder deprecation period than the way 1.6.0 transition was handled, but > that is not (and cannot be) backed by real world experience. Nobody tried > versions of git that warned loudly about the upcoming change every time he > typed "git-commit" to see if the louder deprecation period was really > preferrable. > > We are taking that route for 1.7.0 to warn very loudly about pushing into > the currently checked-out branch in 1.6.2 and onwards. We may now find > out that people hate a loud deprecation period. Then what? Then you get flamed. But isn't that what the maintainer is there for? To take blame on behalf of others, so that contributors can propose what they genuinely believe improvements without fearing what the end users would say? -- Nanako Shiraishi http://ivory.ap.teacup.com/nanako3/ -- 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
