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

[PATCH] Fix a typo in checkout.sh and cleanup one-line help messages

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Dec 11, 2007, 16:36 UTC
Message-ID
<475EBC90.1060606@viscovery.net>
In-Reply-To
<20071211161305.GH15448@artemis.madism.org>
This also shortens option descriptions to fit in 80 columns.
Signed-off-by: Johannes Sixt <johannes.sixt@telecom.at>
---
Pierre Habouzit schrieb:
Show 7 quoted lines
> Signed-off-by: Pierre Habouzit <madcoder@debian.org>
> ---
> 
>   Woops there was another typo in the usage, fix it at the same time.
> 
>  git-checkout.sh |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)

Funny, I had this in my tree since a few days, although embarassingly, I hadn't spotted the "git-branch" typo :-/

-- Hannes
 git-checkout.sh |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/git-checkout.sh b/git-checkout.sh
index f6d58ac..5621c69 100755
--- a/git-checkout.sh
+++ b/git-checkout.sh
@@ -2,13 +2,13 @@

 OPTIONS_KEEPDASHDASH=t
 OPTIONS_SPEC="\
-git-branch [options] [<branch>] [<paths>...]
+git-checkout [options] [<branch>] [<paths>...]
 --
 b=          create a new branch started at <branch>
-l           create the new branchs reflog
-track       tells if the new branch should track the remote branch
+l           create the new branch's reflog
+track       arrange that the new branch tracks the remote branch
 f           proceed even if the index or working tree is not HEAD
-m           performa  three-way merge on local modifications if needed
+m           merge local modifications into the new branch
 q,quiet     be quiet
 "
 SUBDIRECTORY_OK=Sometimes
-- 
1.5.3.7.1079.gecca
Previous: Pierre HabouzitNext: Junio C Hamano
Message 3 of 4 in “stupid typo in git-checkout.sh”
  1. stupid typo in git-checkout.shPierre Habouzit, Dec 11, 2007
  2. Stupid typos in git-checkout.shPierre Habouzit, Dec 11, 2007
  3. Fix a typo in checkout.sh and cleanup one-line help messagesJohannes Sixt, Dec 11, 2007
  4. Junio C HamanoDec 11, 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.