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

[PATCH 1/2] git-worktree.txt: fix missing ")" typo

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Feb 16, 2018, 20:44 UTC
Message-ID
<20180216204452.2153-2-sunshine@sunshineco.com>
In-Reply-To
<20180216204452.2153-1-sunshine@sunshineco.com>

Add the closing ")" to a parenthetical phrase introduced by 4e85333197 (worktree: make add <path> <branch> dwim, 2017-11-26).

While at it, add a missing ":" at the end of the same sentence since it precedes an example literal command block.

Reported-by: Mike Nordell <tamlin.thefirst@gmail.com>
Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
---
 Documentation/git-worktree.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-worktree.txt b/Documentation/git-worktree.txt
index 41585f535d..c941c48827 100644
--- a/Documentation/git-worktree.txt
+++ b/Documentation/git-worktree.txt
@@ -52,10 +52,10 @@ is linked to the current repository, sharing everything except working
 directory specific files such as HEAD, index, etc. `-` may also be
 specified as `<commit-ish>`; it is synonymous with `@{-1}`.
 +
-If <commit-ish> is a branch name (call it `<branch>` and is not found,
+If <commit-ish> is a branch name (call it `<branch>`) and is not found,
 and neither `-b` nor `-B` nor `--detach` are used, but there does
 exist a tracking branch in exactly one remote (call it `<remote>`)
-with a matching name, treat as equivalent to
+with a matching name, treat as equivalent to:
 ------------
 $ git worktree add --track -b <branch> <path> <remote>/<branch>
 ------------
-- 
2.16.1.374.g7648891022
Previous: Eric SunshineNext: Junio C Hamano
Message 3 of 4 in “fix minor git-worktree.txt botches”
  1. 0/2 fix minor git-worktree.txt botchesEric Sunshine, Feb 16, 2018
  2. 2/2 git-worktree.txt: fix indentation of example and text of 'add' commandEric Sunshine, Feb 16, 2018
  3. 1/2 git-worktree.txt: fix missing ")" typoEric Sunshine, Feb 16, 2018
  4. Junio C HamanoFeb 16, 2018

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.