From: Federico Mena Quintero <federico@novell.com>
To: git@vger.kernel.org
Subject: [PATCH 1/4] Mention that git-branch will not automatically check out the new branch
Date: Mon, 17 Sep 2007 20:07:37 -0500 [thread overview]
Message-ID: <1190077657.22387.58.camel@cacharro.xalalinux.org> (raw)
In-Reply-To: <1190077493.22387.54.camel@cacharro.xalalinux.org>
Signed-off-by: Federico Mena Quintero <federico@gnu.org>
---
Documentation/git-branch.txt | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt
index 33bc31b..47e6f49 100644
--- a/Documentation/git-branch.txt
+++ b/Documentation/git-branch.txt
@@ -24,7 +24,9 @@ and option `-a` shows both.
In its second form, a new branch named <branchname> will be created.
It will start out with a head equal to the one given as <start-point>.
If no <start-point> is given, the branch will be created with a head
-equal to that of the currently checked out branch.
+equal to that of the currently checked out branch. Note that this
+will create the new branch, but it will not switch the working tree to
+it; use "git checkout <newbranch>" to switch to the new branch.
When a local branch is started off a remote branch, git can setup the
branch so that gitlink:git-pull[1] will appropriately merge from that
--
1.5.2.4
next prev parent reply other threads:[~2007-09-18 1:05 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 ` Federico Mena Quintero [this message]
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 ` [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=1190077657.22387.58.camel@cacharro.xalalinux.org \
--to=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).