From: Olivier Galibert <galibert@pobox.com>
To: Sean <seanlkml@sympatico.ca>
Cc: git@vger.kernel.org
Subject: Re: [RFC] git-fsck-cache argument processing
Date: Sat, 21 May 2005 20:49:09 +0200 [thread overview]
Message-ID: <20050521184909.GA1729@dspnet.fr.eu.org> (raw)
In-Reply-To: <2015.10.10.10.24.1116696150.squirrel@linux1>
On Sat, May 21, 2005 at 01:22:30PM -0400, Sean wrote:
> Both of these options are generated automatically by argp.
I see. Then I'll guess I'll have to put argp in the "crap" pile next
to libtool and automake.
> I'm sure there
> is a way to override them, but i'd rather just leave them as given by
> argp. For the first case, if you try '-h' on the command line you get:
>
> $ git-fsck-cache -h
> git-fsck-cache: invalid option -- h
> Try `git-fsck-cache --help' or `git-fsck-cache --usage' for more information.
>
> So it leads to the proper help message.
How neat. Of course using the right option under (t)csh gives:
galibert@m62:~ #201 >git-fsck-cache -?
git-fsck-cache: No match.
Importing this windowism is beyond stupid.
OG.
next prev parent reply other threads:[~2005-05-21 18:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-21 3:38 [RFC] git-fsck-cache argument processing Sean
2005-05-21 4:08 ` Jeff Garzik
2005-05-21 4:36 ` Sean
2005-05-21 5:09 ` Jeff Garzik
2005-05-21 5:08 ` Junio C Hamano
2005-05-21 5:15 ` Jeff Garzik
2005-05-21 5:59 ` Junio C Hamano
2005-05-21 15:09 ` Olivier Galibert
2005-05-21 15:35 ` Jeff Garzik
2005-05-21 17:22 ` Sean
2005-05-21 18:49 ` Olivier Galibert [this message]
2005-05-21 19:00 ` Sean
2005-05-21 23:53 ` Jeff Garzik
2005-05-21 22:14 ` Joel Becker
2005-05-21 19:47 ` Linus Torvalds
2005-05-21 20:46 ` Sean
2005-05-21 21:09 ` Sean
2005-05-21 19:49 ` Linus Torvalds
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=20050521184909.GA1729@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--cc=git@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
/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.