From: Jonathan Nieder <jrnieder@gmail.com>
To: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] Documentation/git-pull: clarify configuration
Date: Tue, 9 Nov 2010 21:48:46 -0600 [thread overview]
Message-ID: <20101110034846.GB2401@burratino> (raw)
In-Reply-To: <1289336209-28222-1-git-send-email-martin.von.zweigbergk@gmail.com>
Martin von Zweigbergk wrote:
> The sentence about 'branch.<name>.rebase' refers to the first sentence
> in the paragraph. Clarify by moving it right after that sentence.
Sane.
> --- a/Documentation/git-pull.txt
> +++ b/Documentation/git-pull.txt
> @@ -92,12 +92,11 @@ include::merge-options.txt[]
> :git-pull: 1
>
> --rebase::
> - Instead of a merge, perform a rebase after fetching. If
> - there is a remote ref for the upstream branch, and this branch
> - was rebased since last fetched, the rebase uses that information
> - to avoid rebasing non-local changes. To make this the default
> - for branch `<name>`, set configuration `branch.<name>.rebase`
> - to `true`.
> + Instead of a merge, perform a rebase after fetching. To make this
> + the default for branch `<name>`, set configuration
> + `branch.<name>.rebase` to `true`.
Grammatically, the narrator first gives an order to the git program
("perform a rebase") and then to the person configuring it ("set the
configuration"). Maybe it would be clearer to focus on what the
program does in this case?
Instead of merging, rebase the current branch on top of the
upstream branch after fetching. If there is a remote-tracking
branch corresponding to the upstream branch and the upstream
branch was rebased since last fetched, the rebase uses that
information to avoid rebasing non-local changes.
The default behavior is to merge rather than rebasing, but it
can be overridden per branch with the `branch.<name>.rebase`
configuration item (see git-config(1)).
next prev parent reply other threads:[~2010-11-10 3:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 20:56 [PATCH] Documentation/git-pull: clarify configuration Martin von Zweigbergk
2010-11-10 3:48 ` Jonathan Nieder [this message]
[not found] ` <AANLkTik5MMKWune_i6omu=vXmuVEJqff6Bm0=yNcS9+z@mail.gmail.com>
2010-11-10 17:25 ` When is a patch ready for inclusion? (Re: [PATCH] Documentation/git-pull: clarify configuration) Jonathan Nieder
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=20101110034846.GB2401@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=martin.von.zweigbergk@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).