Paolo Bonzini, Tue, Apr 29, 2008 08:50:15 +0200: >>>>> I can add a global boolean configuration to change the default >>>>> value of skipDefaultRemote. >>>>> >>>> With the default NOT so that current behaviour stays? >>> No, absolutely. In fact if I were you I would set >>> skipDefaultUpdate *now* on the remotes of that repo. >> >> And all the others, who don't read this discussion, are just >> expected to adapt? > > Man, that's what release notes are for. You are expected to read those. > So, a sysadm of a big development site reads them... and faces a big update in all the hundreds of repos (which exists since git-1.4 and were good all this time, BTW). Besides, he faces a need to explain the need for this behavioural change in a really core tool. And, being not really convinced himself that it was needed (I, for one, am not convinced), he finds it real hard. No, I don't have hundreds of repos. Just around 30. And I am (mostly) alone working with them. I still don't like the idea of updating them. -- 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
