From: Federico Mena Quintero <federico@novell.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH 1/4] Say when --track is useful in the git-checkout docs.
Date: Tue, 02 Oct 2007 18:32:32 -0500 [thread overview]
Message-ID: <1191367952.3776.196.camel@cacharro.xalalinux.org> (raw)
In-Reply-To: <1191367817.3776.192.camel@cacharro.xalalinux.org>
The documentation used to say what the option does, but it
didn't mention a use case.
Signed-off-by: Federico Mena Quintero <federico@gnu.org>
---
Documentation/git-checkout.txt | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt
index 734928b..dbd1a4a 100644
--- a/Documentation/git-checkout.txt
+++ b/Documentation/git-checkout.txt
@@ -50,7 +50,9 @@ 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. Use this if you always
+ pull from the same remote branch into the new branch, or if you
+ don't want to use "git pull <repository> <refspec>" 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.
--
1.5.2.4
next prev parent reply other threads:[~2007-10-02 23:31 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
2007-10-02 23:30 ` [PATCH 0/4] Another round of the --track patches Federico Mena Quintero
2007-10-02 23:32 ` Federico Mena Quintero [this message]
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=1191367952.3776.196.camel@cacharro.xalalinux.org \
--to=federico@novell.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).