From: Junio C Hamano <gitster@pobox.com>
To: jari.aalto@cante.net
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-pull.txt: Mention branch.autosetuprebase
Date: Fri, 03 Dec 2010 11:36:57 -0800 [thread overview]
Message-ID: <7v1v5yps12.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1291364454-9849-1-git-send-email-jari.aalto@cante.net> (jari aalto's message of "Fri\, 3 Dec 2010 10\:20\:54 +0200")
jari.aalto@cante.net writes:
> From: Jari Aalto <jari.aalto@cante.net>
>
> In "Options related to merging" mention also related option
> branch.autosetuprebase in git-config(1).
>
> Signed-off-by: Jari Aalto <jari.aalto@cante.net>
> ---
> Documentation/git-pull.txt | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt
> index e47361f..7b4caac 100644
> --- a/Documentation/git-pull.txt
> +++ b/Documentation/git-pull.txt
> @@ -98,8 +98,9 @@ include::merge-options.txt[]
> fetched, the rebase uses that information to avoid rebasing
> non-local changes.
> +
> -See `branch.<name>.rebase` in linkgit:git-config[1] if you want to make
> -`git pull` always use `{litdd}rebase` instead of merging.
> +See `branch.<name>.rebase` and `branch.autosetuprebase` in
> +linkgit:git-config[1] if you want to make `git pull` always use
> +`{litdd}rebase` instead of merging.
Thanks; will queue.
prev parent reply other threads:[~2010-12-03 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 8:20 [PATCH] git-pull.txt: Mention branch.autosetuprebase jari.aalto
2010-12-03 14:57 ` Jakub Narebski
2010-12-03 19:36 ` 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=7v1v5yps12.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
/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).