remote: fix set-branches usage and documentation
The canonical order of command line arguments is always to have dashed commands before other parameters, but the "git remote set-branches" subcommand was described to take "name" before an optional "--add". Signed-off-by: Philip Jägenstedt <philip@foolip.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Philip Jägenstedt committed
Feb 18, 2012 at 12:17 UTC
ca5bc9e61fb26969c9b028c9b853af109f9f00c5
2 files changed
+2
-2
Documentation/git-remote.txt
+1
-1
@@ -14,7 +14,7 @@ SYNOPSIS
14
'git remote rename' <old> <new>
15
'git remote rm' <name>
16
'git remote set-head' <name> (-a | -d | <branch>)
17
-'git remote set-branches' <name> [--add] <branch>...
17
+'git remote set-branches' [--add] <name> <branch>...
18
'git remote set-url' [--push] <name> <newurl> [<oldurl>]
19
'git remote set-url --add' [--push] <name> <newurl>
20
'git remote set-url --delete' [--push] <name> <url>
builtin/remote.c
+1
-1
@@ -16,7 +16,7 @@ static const char * const builtin_remote_usage[] = {
16
"git remote [-v | --verbose] show [-n] <name>",
17
"git remote prune [-n | --dry-run] <name>",
18
"git remote [-v | --verbose] update [-p | --prune] [group | remote]",
19
- "git remote set-branches <name> [--add] <branch>...",
19
+ "git remote set-branches [--add] <name> <branch>...",
20
"git remote set-url <name> <newurl> [<oldurl>]",
21
"git remote set-url --add <name> <newurl>",
22
"git remote set-url --delete <name> <url>",