Documentation/git-rebase.txt: make it explicit in the syntax there is no way to specify <branch> without <upstream>.
PATCH 1/1 Documentation/git-rebase.txt: make it explicit in the syntax there is no way to specify <branch> without <upstream>.
Current syntax description makes one wonder if there is any syntactic way to distinguish between <branch> and <upstream> so that one can specify <branch> but not <upstream>. The change makes it explicit that these arguments are in fact positional.
Signed-off-by Sergey Organov <[email protected]>
--- Documentation/git-rebase.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/git-rebase.txt +1 -1
@@ -9,7 +9,7 @@ SYNOPSIS -------- [verse] 'git rebase' [-i | --interactive] [options] [--exec <cmd>] [--onto <newbase>] - [<upstream>] [<branch>] + [<upstream> [<branch>]] 'git rebase' [-i | --interactive] [options] [--exec <cmd>] [--onto <newbase>] --root [<branch>] 'git rebase' --continue | --skip | --abort | --edit-todo
Signature · 1 line
1.9.3
Quoted 4 lines · Sergey Organov
Current syntax description makes one wonder if there is any syntactic way to distinguish between <branch> and <upstream> so that one can specify <branch> but not <upstream>. The change makes it explicit that these arguments are in fact positional.
Makes sense.
Thanks.
Quoted 19 lines
Signed-off-by Sergey Organov <[email protected]>--- Documentation/git-rebase.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Documentation/git-rebase.txt +1
-1@@ -9,7 +9,7 @@ SYNOPSIS -------- [verse] 'git rebase' [-i | --interactive] [options] [--exec <cmd>] [--onto <newbase>] - [<upstream>] [<branch>] + [<upstream> [<branch>]] 'git rebase' [-i | --interactive] [options] [--exec <cmd>] [--onto <newbase>] --root [<branch>] 'git rebase' --continue | --skip | --abort | --edit-todo