Browse Source
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>maint
Finn Arne Gangstad
16 years ago
committed by
Junio C Hamano
2 changed files with 9 additions and 3 deletions
Loading…
Reference in new issue