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

[PATCH 13/16] contrib/examples: make usage text consistent

From
David Aguilar <davvid@gmail.com>
Date
Feb 24, 2013, 00:20 UTC
Message-ID
<1361665254-42866-14-git-send-email-davvid@gmail.com>
In-Reply-To
<1361665254-42866-13-git-send-email-davvid@gmail.com>
Use a lowercase "usage:" string for consistency with Git.
Signed-off-by: David Aguilar <davvid@gmail.com>
---
 contrib/examples/git-remote.perl    | 2 +-
 contrib/examples/git-svnimport.perl | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/contrib/examples/git-remote.perl b/contrib/examples/git-remote.perl
index b17952a..b549a3c 100755
--- a/contrib/examples/git-remote.perl
+++ b/contrib/examples/git-remote.perl
@@ -347,7 +347,7 @@ sub rm_remote {
 }
 
 sub add_usage {
-	print STDERR "Usage: git remote add [-f] [-t track]* [-m master] <name> <url>\n";
+	print STDERR "usage: git remote add [-f] [-t track]* [-m master] <name> <url>\n";
 	exit(1);
 }
 
diff --git a/contrib/examples/git-svnimport.perl b/contrib/examples/git-svnimport.perl
index b09ff8f..c414f0d 100755
--- a/contrib/examples/git-svnimport.perl
+++ b/contrib/examples/git-svnimport.perl
@@ -36,7 +36,7 @@ our($opt_h,$opt_o,$opt_v,$opt_u,$opt_C,$opt_i,$opt_m,$opt_M,$opt_t,$opt_T,
 
 sub usage() {
 	print STDERR <<END;
-Usage: ${\basename $0}     # fetch/update GIT from SVN
+usage: ${\basename $0}     # fetch/update GIT from SVN
        [-o branch-for-HEAD] [-h] [-v] [-l max_rev] [-R repack_each_revs]
        [-C GIT_repository] [-t tagname] [-T trunkname] [-b branchname]
        [-d|-D] [-i] [-u] [-r] [-I ignorefilename] [-s start_chg]
-- 
1.8.2.rc0.247.g811e0c0
Previous: David AguilarNext: David Aguilar
Message 14 of 20 in “make usage text consistent in git commands”
  1. 00/16 make usage text consistent in git commandsDavid Aguilar, Feb 24, 2013
  2. 01/16 git-sh-setup: make usage text consistentDavid Aguilar, Feb 24, 2013
  3. 02/16 git-svn: make usage text consistentDavid Aguilar, Feb 24, 2013
  4. 03/16 git-relink: make usage text consistentDavid Aguilar, Feb 24, 2013
  5. 04/16 git-merge-one-file: make usage text consistentDavid Aguilar, Feb 24, 2013
  6. 05/16 git-archimport: make usage text consistentDavid Aguilar, Feb 24, 2013
  7. 06/16 git-cvsexportcommit: make usage text consistentDavid Aguilar, Feb 24, 2013
  8. 07/16 git-cvsimport: make usage text consistentDavid Aguilar, Feb 24, 2013
  9. 08/16 git-cvsimport: make usage text consistentDavid Aguilar, Feb 24, 2013
  10. 09/16 contrib/credential: make usage text consistentDavid Aguilar, Feb 24, 2013
  11. 10/16 contrib/fast-import: make usage text consistentDavid Aguilar, Feb 24, 2013
  12. 11/16 contrib/fast-import/import-zips.py: fix broken error messageDavid Aguilar, Feb 24, 2013
  13. 12/16 contrib/fast-import/import-zips.py: use spaces instead of tabsDavid Aguilar, Feb 24, 2013
  14. 13/16 contrib/examples: make usage text consistentDavid Aguilar, Feb 24, 2013
  15. 14/16 contrib/hooks/setgitperms.perl: make usage text consistentDavid Aguilar, Feb 24, 2013
  16. 15/16 templates/hooks--update.sample: make usage text consistentDavid Aguilar, Feb 24, 2013
  17. 16/16 Documentation/user-manual.txt: make usage text consistentDavid Aguilar, Feb 24, 2013
  18. Jonathan NiederFeb 24, 2013
  19. Jonathan NiederFeb 24, 2013
  20. David AguilarFeb 24, 2013

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.