{"thread":{"id":"37578","subject":"[PATCH] Documentation/git-rebase.txt: make it explicit in the syntax there is no way to specify <branch> without <upstream>.","startedAt":"2014-08-29T13:51:46Z","lastAt":"2014-09-16T18:26:39Z","messageCount":2,"participants":["Sergey Organov","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"249506","messageId":"87fvfrlg86.fsf@osv.gnss.ru","threadId":"37578","inReplyTo":null,"subject":"[PATCH] Documentation/git-rebase.txt: make it explicit in the syntax there is no way to specify <branch> without <upstream>.","fromName":"Sergey Organov","fromEmail":"sorganov@gmail.com","sentAt":"2014-08-29T13:51:46Z","receivedAt":"2014-08-29T13:51:46Z","isPatch":true,"sender":{"key":"sorganov@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8501568?v=4"},"body":"Current syntax description makes one wonder if there is any syntactic way\nto distinguish between <branch> and <upstream> so that one can specify\n<branch> but not <upstream>. The change makes it explicit that these\narguments are in fact positional.\n\nSigned-off-by: Sergey Organov <sorganov@gmail.com>\n---\n Documentation/git-rebase.txt | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt\nindex f14100a..4138554 100644\n--- a/Documentation/git-rebase.txt\n+++ b/Documentation/git-rebase.txt\n@@ -9,7 +9,7 @@ SYNOPSIS\n --------\n [verse]\n 'git rebase' [-i | --interactive] [options] [--exec <cmd>] [--onto <newbase>]\n-\t[<upstream>] [<branch>]\n+\t[<upstream> [<branch>]]\n 'git rebase' [-i | --interactive] [options] [--exec <cmd>] [--onto <newbase>]\n \t--root [<branch>]\n 'git rebase' --continue | --skip | --abort | --edit-todo\n-- \n1.9.3\n"},{"id":"249513","messageId":"xmqqiokn2zhc.fsf@gitster.dls.corp.google.com","threadId":"37578","inReplyTo":"87fvfrlg86.fsf@osv.gnss.ru","subject":"Re: [PATCH] Documentation/git-rebase.txt: make it explicit in the syntax there is no way to specify <branch> without <upstream>.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2014-09-16T18:26:39Z","receivedAt":"2014-09-16T18:26:39Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Sergey Organov <sorganov@gmail.com> writes:\n\n> Current syntax description makes one wonder if there is any syntactic way\n> to distinguish between <branch> and <upstream> so that one can specify\n> <branch> but not <upstream>. The change makes it explicit that these\n> arguments are in fact positional.\n\nMakes sense.\nThanks.\n\n\n>\n> Signed-off-by: Sergey Organov <sorganov@gmail.com>\n> ---\n>  Documentation/git-rebase.txt | 2 +-\n>  1 file changed, 1 insertion(+), 1 deletion(-)\n>\n> diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt\n> index f14100a..4138554 100644\n> --- a/Documentation/git-rebase.txt\n> +++ b/Documentation/git-rebase.txt\n> @@ -9,7 +9,7 @@ SYNOPSIS\n>  --------\n>  [verse]\n>  'git rebase' [-i | --interactive] [options] [--exec <cmd>] [--onto <newbase>]\n> -\t[<upstream>] [<branch>]\n> +\t[<upstream> [<branch>]]\n>  'git rebase' [-i | --interactive] [options] [--exec <cmd>] [--onto <newbase>]\n>  \t--root [<branch>]\n>  'git rebase' --continue | --skip | --abort | --edit-todo\n"}]}