Re: Suggestion: git fetch <remote> <branch> to update remote-tracking branch

Antony Male <antony.male@gmail.com> writes:

I think this was discussed number of times here, and my vague recollection of the conclusion last time is that it would be OK to change the behaviour of single-shot fetch "fetch <remote> <branch>" against a remote where there is already a default fetch refspec that covers the <branch> so that such a fetch will update the remote tracking branch that usually copies from <branch> (and only that one).

We might need a proper deprecation and migration plan, though. I say "might" because offhand I don't know what the extent of damages to existing users' habits will be if we didn't offer any.