From: Junio C Hamano <gitster@pobox•com>
To: Sergey Organov <sorganov@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] Documentation/git-rebase.txt: make it explicit in the syntax there is no way to specify <branch> without <upstream>.
Date: Tue, 16 Sep 2014 11:26:39 -0700 [thread overview]
Message-ID: <xmqqiokn2zhc.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <87fvfrlg86.fsf@osv.gnss.ru> (Sergey Organov's message of "Fri, 29 Aug 2014 17:51:46 +0400")
Sergey Organov <sorganov@gmail•com> writes:
> 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.
>
> Signed-off-by: Sergey Organov <sorganov@gmail•com>
> ---
> Documentation/git-rebase.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
> index f14100a..4138554 100644
> --- a/Documentation/git-rebase.txt
> +++ b/Documentation/git-rebase.txt
> @@ -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
prev parent reply other threads:[~2014-09-16 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 13:51 [PATCH] Documentation/git-rebase.txt: make it explicit in the syntax there is no way to specify <branch> without <upstream> Sergey Organov
2014-09-16 18:26 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqiokn2zhc.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=sorganov@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox