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

[PATCH] branch doc: consistently promote 'switch'

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 3, 2026, 21:58 UTC
Message-ID
<xmqqwlqt4lwj.fsf@gitster.g>

When 328c6cb853 (doc: promote "git switch", 2019-03-29) updated an example in git-branch documentation, it made an inconsistent change to turn "git checkout my2.6.14" command in an example into "git switch my2.6.14", without updating a comment that talks about a shorthand to create and checkout the newly created branch at the same time, which still talked about "checkout -b <new> <start>".

Update the latter to talk about "git switch -c" for consistency.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 * An alternative would be to list both "git checkout -b" and "git
   switch -c", as "git checkout" is not going away (for the purpose
   of *replacing* checkout, the switch/restore were a failed
   experiment, even though they gained enough users to stay).
 Documentation/git-branch.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git c/Documentation/git-branch.adoc w/Documentation/git-branch.adoc
index bfdf459329..a803c24858 100644
--- c/Documentation/git-branch.adoc
+++ w/Documentation/git-branch.adoc
@@ -406,17 +406,17 @@ Start development from a known tag::
 ------------
 $ git clone git://git.kernel.org/pub/scm/.../linux-2.6 my2.6
 $ cd my2.6
 $ git branch my2.6.14 v2.6.14   <1>
 $ git switch my2.6.14
 ------------
 +
 <1> This step and the next one could be combined into a single step with
-    "checkout -b my2.6.14 v2.6.14".
+    "git switch -c my2.6.14 v2.6.14".
 
 Delete an unneeded branch::
 +
 ------------
 $ git clone git://git.kernel.org/.../git.git my.git
 $ cd my.git
 $ git branch -d -r origin/todo origin/html origin/man   <1>
 $ git branch -D test                                    <2>
Next: Ben Knoble
Message 1 of 2 in “branch doc: consistently promote 'switch'”
  1. branch doc: consistently promote 'switch'Junio C Hamano, Nov 3, 2026
  2. Ben KnobleNov 4, 2026

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.