On Tue, Apr 29, 2008 at 11:26:46PM +0100, Johannes Schindelin wrote: > I wonder why you need to make such a big change, which _is_ incompatible, > and not do the obvious thing, namely introduce a subcommand to "git > remote" which does the "push" equivalent of "git remote update"... > > Do you really think that it is a good idea to push down a huge change like > this down everybody else's throat, just because you do not want to type > "git remote ..." but "git fetch ..." in your workflow? I wonder this a bit, too, and I am even somebody who _likes_ the new behavior. But there is a difference between "should have been designed this way in the first place" and "is currently designed some other way, and will cause pain to switch it to this way." So it might simply not be worth the trouble to change. OTOH, I think this is how we end up with many commands to do slightly different things, which can end up confusing new users. I'm not sure what the right answer is. -Peff -- 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
