git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 1/4] Mention that git-branch will not automatically check out the new branch

From
FQFederico Mena Quintero <federico@novell.com>
Date
Sep 18, 2007, 01:07 UTC
Message-ID
<1190077657.22387.58.camel@cacharro.xalalinux.org>
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
Previous: Federico Mena QuinteroNext: Federico Mena Quintero
Message 2 of 13 in “Make the documentation consistent for --track and --notrack”
  1. 0/4 Make the documentation consistent for --track and --notrackFederico Mena Quintero, Sep 18, 2007
  2. 1/4 Mention that git-branch will not automatically check out the new branchFederico Mena Quintero, Sep 18, 2007
  3. 2/4 Copy the docs for --track and --notrack from git-checkout to git-branchFederico Mena Quintero, Sep 18, 2007
  4. 3/4 Mention the parameters that git-pull would need to be equivalent to a --track in the git-checkout docsFederico Mena Quintero, Sep 18, 2007
  5. Junio C HamanoSep 18, 2007
  6. 0/4 Another round of the --track patchesFederico Mena Quintero, Oct 2, 2007
  7. 1/4 Say when --track is useful in the git-checkout docs.Federico Mena Quintero, Oct 2, 2007
  8. 1/4 Add documentation for --track and --no-track to the git-branch docs.Federico Mena Quintero, Oct 2, 2007
  9. Federico Mena QuinteroOct 2, 2007
  10. 3/4 Note that git-branch will not automatically checkout the new branchFederico Mena Quintero, Oct 2, 2007
  11. 4/4 Make git-pull complain and give advice when there is nothing to pull fromFederico Mena Quintero, Oct 2, 2007
  12. 4/4 Make git-pull give hints on what to do when there is no branch to merge fromFederico Mena Quintero, Sep 18, 2007
  13. Junio C HamanoSep 18, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.