From: "Karl Hasselström" <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: [PATCH 1/3] Let "stg help" be like "stg --help"
Date: Sun, 22 Oct 2006 15:05:21 +0200 [thread overview]
Message-ID: <20061022130520.16449.70729.stgit@localhost> (raw)
In-Reply-To: <20061022130214.16449.41482.stgit@localhost>
From: Karl Hasselström <kha@treskal.com>
"stg --help" prints the list of commands, but "stg help" just prints
the usage message for the help command. This may be useful in theory,
but the distinction is probably lost on 95% of all users (and the
remaining 5% probably don't need to see the usage message for the help
command anyway, since they know how it works). So just make both
commands output the helpful command list.
Signed-off-by: Karl Hasselström <kha@treskal.com>
---
stgit/main.py | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/stgit/main.py b/stgit/main.py
index de35ca8..66128a3 100644
--- a/stgit/main.py
+++ b/stgit/main.py
@@ -226,8 +226,7 @@ def main():
option_list = command.options)
parser.print_help()
else:
- print 'usage: %s help <command>' % prog
-
+ print_help()
sys.exit(0)
if cmd in ['-v', '--version', 'version']:
print 'Stacked GIT %s' % version
next prev parent reply other threads:[~2006-10-22 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 13:02 [PATCH 0/3] Fix a few rough spots in StGIT's help command Karl Hasselström
2006-10-22 13:05 ` Karl Hasselström [this message]
2006-10-22 13:05 ` [PATCH 2/3] When no command was given, print usage message Karl Hasselström
2006-10-22 13:05 ` [PATCH 3/3] Disregard extraneous arguments when providing help Karl Hasselström
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=20061022130520.16449.70729.stgit@localhost \
--to=kha@treskal.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).