From: Junio C Hamano <gitster@pobox.com>
To: Federico Mena Quintero <federico@novell.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/4] Mention the parameters that git-pull would need to be equivalent to a --track in the git-checkout docs
Date: Tue, 18 Sep 2007 15:38:27 -0700 [thread overview]
Message-ID: <7v3axbvbto.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1190077881.22387.63.camel@cacharro.xalalinux.org> (Federico Mena Quintero's message of "Mon, 17 Sep 2007 20:11:21 -0500")
Federico Mena Quintero <federico@novell.com> writes:
> To be consistent with the git-branch docs.
>
> Signed-off-by: Federico Mena Quintero <federico@gnu.org>
> ---
> Documentation/git-checkout.txt | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt
> index 734928b..6f22626 100644
> --- a/Documentation/git-checkout.txt
> +++ b/Documentation/git-checkout.txt
> @@ -50,7 +50,8 @@ OPTIONS
> --track::
> When -b is given and a branch is created off a remote branch,
> set up configuration so that git-pull will automatically
> - retrieve data from the remote branch. Set the
> + retrieve data from the remote branch, otherwise you'll have to
> + use "git pull <url>" explicitly. Set the
> branch.autosetupmerge configuration variable to true if you
> want git-checkout and git-branch to always behave as if
> '--track' were given.
Hmph.
I'd rather make them consistent by dropping the not-so-correct
"otherwise" phrase from all three copies. It is not "otherwise
you'll have to", but "instead you can".
next prev parent reply other threads:[~2007-09-18 22:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 1:04 [PATCH 0/4] Make the documentation consistent for --track and --notrack Federico Mena Quintero
2007-09-18 1:07 ` [PATCH 1/4] Mention that git-branch will not automatically check out the new branch Federico Mena Quintero
2007-09-18 1:10 ` [PATCH 2/4] Copy the docs for --track and --notrack from git-checkout to git-branch Federico Mena Quintero
2007-09-18 1:11 ` [PATCH 3/4] Mention the parameters that git-pull would need to be equivalent to a --track in the git-checkout docs Federico Mena Quintero
2007-09-18 22:38 ` Junio C Hamano [this message]
2007-10-02 23:30 ` [PATCH 0/4] Another round of the --track patches Federico Mena Quintero
2007-10-02 23:32 ` [PATCH 1/4] Say when --track is useful in the git-checkout docs Federico Mena Quintero
2007-10-02 23:33 ` [PATCH 1/4] Add documentation for --track and --no-track to the git-branch docs Federico Mena Quintero
2007-10-02 23:35 ` Federico Mena Quintero
2007-10-02 23:34 ` [PATCH 3/4] Note that git-branch will not automatically checkout the new branch Federico Mena Quintero
2007-10-02 23:36 ` [PATCH 4/4] Make git-pull complain and give advice when there is nothing to pull from Federico Mena Quintero
2007-09-18 1:12 ` [PATCH 4/4] Make git-pull give hints on what to do when there is no branch to merge from Federico Mena Quintero
2007-09-18 23:00 ` Junio C Hamano
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=7v3axbvbto.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=federico@novell.com \
--cc=git@vger.kernel.org \
/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).