From: Junio C Hamano <junkio@cox.net>
To: Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: git log is a bit antisocial
Date: Fri, 14 Apr 2006 14:28:02 -0700 [thread overview]
Message-ID: <7vhd4vq23h.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0604141719290.2215@localhost.localdomain> (Nicolas Pitre's message of "Fri, 14 Apr 2006 17:20:13 -0400 (EDT)")
Nicolas Pitre <nico@cam.org> writes:
> On Fri, 14 Apr 2006, Junio C Hamano wrote:
>
>> Nicolas Pitre <nico@cam.org> writes:
>>
>> > $ git log -h
>> > fatal: unrecognized argument: -h
>> > $ git log --help
>> > fatal: unrecognized argument: --help
>> >
>> > Maybe the usage string could be printed in those cases?
>>
>> Perhaps. Alternatively, "git help log", perhaps.
>
> What about git-log then?
What about it?
Asking for help on log could be spelled as "git log --help" with
a patch like the attached, but I am not sure that is worth it...
-- >8 --
diff --git a/git.c b/git.c
index 78ed403..7fdacdd 100644
--- a/git.c
+++ b/git.c
@@ -497,6 +497,16 @@ int main(int argc, const char **argv, ch
}
argv[0] = cmd;
+ /* It could be git blah --help or git boo -h, but be
+ * careful; most commands have their own '-h' and '--help'.
+ */
+ if (argc == 2 &&
+ (!strcmp(argv[1], "-h") || !strcmp(argv[1], "--help"))) {
+ argv[0] = "help";
+ argv[1] = cmd;
+ exit(cmd_help(1, argv, envp));
+ }
+
/*
* We search for git commands in the following order:
* - git_exec_path()
next prev parent reply other threads:[~2006-04-14 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 20:50 git log is a bit antisocial Nicolas Pitre
2006-04-14 20:56 ` Junio C Hamano
2006-04-14 21:20 ` Nicolas Pitre
2006-04-14 21:28 ` Junio C Hamano [this message]
2006-04-14 21:44 ` Sébastien Pierre
2006-04-14 22:06 ` Junio C Hamano
2006-04-14 22:15 ` Sébastien Pierre
2006-04-14 22:45 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vhd4vq23h.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=nico@cam.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).