From: Junio C Hamano <junkio@cox.net>
To: Kevin Geiss <kevin@desertsol.com>
Cc: martin.langhoff@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH 1/1] git-cvsexportcommit.perl: Fix usage() output.
Date: Mon, 14 Nov 2005 14:14:40 -0800 [thread overview]
Message-ID: <7vbr0mx4fj.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051114164505.GF9131@raven.localdomain> (Kevin Geiss's message of "Mon, 14 Nov 2005 09:45:05 -0700")
Kevin Geiss <kevin@desertsol.com> writes:
> sub usage {
> print STDERR <<END;
> -Usage: GIT_DIR=/path/to/.gi ${\basename $0} # fetch/update GIT from CVS
> - [-h] [-p] [ parent ] commit
> +Usage: GIT_DIR=/path/to/.git ${\basename $0} [-h] [-p] [-v] [-c] [ parent ] commit
> END
> exit(1);
> }
I hate to be nitpicky, but this slurps in File::Basename
(9Kbytes) only to shorten the displayed command name.
I personally do not like programs that shorten $0 (or in C
argv[0]) when they identify themselves. This is probably just
me, but I was bitten by such programs too many times while
debugging them, after wasting too many hours only to find that I
was not running the executable I thought I was running but
something else that happened to be earlier on my PATH X-<.
next prev parent reply other threads:[~2005-11-14 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 16:40 eth Kevin Geiss
2005-11-14 16:45 ` [PATCH 1/1] git-cvsexportcommit.perl: Fix usage() output Kevin Geiss
2005-11-14 20:24 ` Kevin Geiss
2005-11-14 22:14 ` Junio C Hamano [this message]
2005-11-14 22:20 ` Martin Langhoff
2005-11-14 23:04 ` Junio C Hamano
2005-11-15 5:10 ` Martin Langhoff
2005-11-14 16:47 ` eth Kevin Geiss
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=7vbr0mx4fj.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=kevin@desertsol.com \
--cc=martin.langhoff@gmail.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 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).