git remote update: Fallback to remote if group does not exist
commitb344e1614b15dfde0ab4dfc175bed1aac39bc264
authorFinn Arne Gangstad <finnag@pvv.org>
Mon, 6 Apr 2009 13:41:02 +0000 (6 15:41 +0200)
committerJunio C Hamano <gitster@pobox.com>
Wed, 8 Apr 2009 04:52:26 +0000 (7 21:52 -0700)
treef10a28791949617e5075d635fb67ecb851d0e121
parent9a23ba3375e2afa8045a433a3debce99c373beb2
git remote update: Fallback to remote if group does not exist

Previously, git remote update <remote> would fail unless there was
a remote group configured with the same name as the remote.
git remote update will now fall back to using the remote if no matching
group can be found.

This enables "git remote update -p <remote>..." to fetch and prune one
or more remotes, for example.

Signed-off-by: Finn Arne Gangstad <finnag@pvv.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-remote.txt
builtin-remote.c