From: "Sean" <seanlkml@sympatico.ca>
To: "Olivier Galibert" <galibert@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] git-fsck-cache argument processing
Date: Sat, 21 May 2005 13:22:30 -0400 (EDT) [thread overview]
Message-ID: <2015.10.10.10.24.1116696150.squirrel@linux1> (raw)
In-Reply-To: <20050521150926.GA96606@dspnet.fr.eu.org>
On Sat, May 21, 2005 11:09 am, Olivier Galibert said:
> On Fri, May 20, 2005 at 11:38:52PM -0400, Sean wrote:
>> -?, --help Give this help list
>
> Could you make that '-h' please ?
>
>> -V, --version Print program version
>
> And that '-v'. -V traditionally means verbose, -v version. Yes, I
> know there are counter-examples, but statistically...
>
Hey Olivier,
Both of these options are generated automatically by argp. 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.
Sean
next prev parent reply other threads:[~2005-05-21 17:21 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 [this message]
2005-05-21 18:49 ` Olivier Galibert
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=2015.10.10.10.24.1116696150.squirrel@linux1 \
--to=seanlkml@sympatico.ca \
--cc=galibert@pobox.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 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.