On Tue, Oct 20, 2009 at 11:33:40PM -0700, Junio C Hamano wrote: > Mike Hommey <mh@xxxxxxxxxxxx> writes: > > > BTW, shouldn't fetch be deprecated in favour of git remote update ? > > Why? People will then be confused because half of them would expect > "remote update" to somehow affect their working tree, and some others > would expect their working tree reset to one of the branches from the > remote, and it won't solve anything. I must be missing the obvious but which one of fetch and remote update does the above ? I was under the impression that none of them would. > Oh, and it will irritate people who > are used to type "git fetch", too. That's another problem, but my understanding is that git fetch and git remote update are roughly doing the same thing. Having two commands for the same thing is confusing. I kind of like the idea to have one command, remote, to handle, err, remotes. Also note that I said deprecated, not remove ; that could mean keeping fetch, but pushing the use of remote update for new users. Mike -- 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