From: David Aguilar <davvid@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH 10/16] contrib/fast-import: make usage text consistent
Date: Sat, 23 Feb 2013 16:20:48 -0800 [thread overview]
Message-ID: <1361665254-42866-11-git-send-email-davvid@gmail.com> (raw)
In-Reply-To: <1361665254-42866-10-git-send-email-davvid@gmail.com>
Use a lowercase "usage:" string for consistency with Git.
Signed-off-by: David Aguilar <davvid@gmail.com>
---
contrib/fast-import/git-import.perl | 2 +-
contrib/fast-import/git-import.sh | 2 +-
contrib/fast-import/import-zips.py | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/contrib/fast-import/git-import.perl b/contrib/fast-import/git-import.perl
index f9fef6d..0891b9e 100755
--- a/contrib/fast-import/git-import.perl
+++ b/contrib/fast-import/git-import.perl
@@ -7,7 +7,7 @@
use strict;
use File::Find;
-my $USAGE = 'Usage: git-import branch import-message';
+my $USAGE = 'usage: git-import branch import-message';
my $branch = shift or die "$USAGE\n";
my $message = shift or die "$USAGE\n";
diff --git a/contrib/fast-import/git-import.sh b/contrib/fast-import/git-import.sh
index 0ca7718..f8d803c 100755
--- a/contrib/fast-import/git-import.sh
+++ b/contrib/fast-import/git-import.sh
@@ -5,7 +5,7 @@
# but is meant to be a simple fast-import example.
if [ -z "$1" -o -z "$2" ]; then
- echo "Usage: git-import branch import-message"
+ echo "usage: git-import branch import-message"
exit 1
fi
diff --git a/contrib/fast-import/import-zips.py b/contrib/fast-import/import-zips.py
index 5cec9b0..f54c65b 100755
--- a/contrib/fast-import/import-zips.py
+++ b/contrib/fast-import/import-zips.py
@@ -19,7 +19,7 @@ if hexversion < 0x01060000:
sys.exit(1)
if len(argv) < 2:
- print 'Usage:', argv[0], '<zipfile>...'
+ print 'usage:', argv[0], '<zipfile>...'
exit(1)
branch_ref = 'refs/heads/import-zips'
--
1.8.2.rc0.247.g811e0c0
next prev parent reply other threads:[~2013-02-24 0:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 0:20 [PATCH 00/16] make usage text consistent in git commands David Aguilar
2013-02-24 0:20 ` [PATCH 01/16] git-sh-setup: make usage text consistent David Aguilar
2013-02-24 0:20 ` [PATCH 02/16] git-svn: " David Aguilar
2013-02-24 0:20 ` [PATCH 03/16] git-relink: " David Aguilar
2013-02-24 0:20 ` [PATCH 04/16] git-merge-one-file: " David Aguilar
2013-02-24 0:20 ` [PATCH 05/16] git-archimport: " David Aguilar
2013-02-24 0:20 ` [PATCH 06/16] git-cvsexportcommit: " David Aguilar
2013-02-24 0:20 ` [PATCH 07/16] git-cvsimport: " David Aguilar
2013-02-24 0:20 ` [PATCH 08/16] " David Aguilar
2013-02-24 0:20 ` [PATCH 09/16] contrib/credential: " David Aguilar
2013-02-24 0:20 ` David Aguilar [this message]
2013-02-24 0:20 ` [PATCH 11/16] contrib/fast-import/import-zips.py: fix broken error message David Aguilar
2013-02-24 0:20 ` [PATCH 12/16] contrib/fast-import/import-zips.py: use spaces instead of tabs David Aguilar
2013-02-24 0:20 ` [PATCH 13/16] contrib/examples: make usage text consistent David Aguilar
2013-02-24 0:20 ` [PATCH 14/16] contrib/hooks/setgitperms.perl: " David Aguilar
2013-02-24 0:20 ` [PATCH 15/16] templates/hooks--update.sample: " David Aguilar
2013-02-24 0:20 ` [PATCH 16/16] Documentation/user-manual.txt: " David Aguilar
2013-02-24 0:25 ` [PATCH 01/16] git-sh-setup: " Jonathan Nieder
2013-02-24 0:29 ` [PATCH 00/16] make usage text consistent in git commands Jonathan Nieder
2013-02-24 0:37 ` David Aguilar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1361665254-42866-11-git-send-email-davvid@gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.