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

[PATCH] Call out the two different uses of git-branch and fix a typo.

From
Jon Loeliger <jdl@jdl.com>
Date
Mar 18, 2006, 00:24 UTC
Message-ID
<E1FKPFF-00061q-4Y@jdl.com>
Signed-off-by: Jon Loeliger <jdl@jdl.com>
---
 Documentation/git-branch.txt |   10 +++++++---
 1 files changed, 7 insertions(+), 3 deletions(-)
1a4336ee2a807d4ccc23d97c7b5c2dce2d4ef116
diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt
index 4cd0cb9..71ecd85 100644
--- a/Documentation/git-branch.txt
+++ b/Documentation/git-branch.txt
@@ -7,16 +7,20 @@ git-branch - Create a new branch, or rem
 
 SYNOPSIS
 --------
-'git-branch' [(-d | -D) <branchname>] | [[-f] <branchname> [<start-point>]]
+[verse]
+'git-branch' [[-f] <branchname> [<start-point>]]
+'git-branch' (-d | -D) <branchname>
 
 DESCRIPTION
 -----------
 If no argument is provided, show available branches and mark current
 branch with star. Otherwise, create a new branch of name <branchname>.
-
 If a starting point is also specified, that will be where the branch is
 created, otherwise it will be created at the current HEAD.
 
+With a `-d` or `-D` option, `<branchname>` will be deleted.
+
+
 OPTIONS
 -------
 -d::
@@ -39,7 +43,7 @@ OPTIONS
 Examples
 ~~~~~~~~
 
-Start development off of a know tag::
+Start development off of a known tag::
 +
 ------------
 $ git clone git://git.kernel.org/pub/scm/.../linux-2.6 my2.6
-- 
1.2.4.gdd7be
Message 1 of 1 in “Call out the two different uses of git-branch and fix a typo.”
  1. Call out the two different uses of git-branch and fix a typo.Jon Loeliger, Mar 18, 2006

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.