From: Ed L Cashin <ecashin@coraid.com>
To: git@vger.kernel.org
Subject: Re: [RFH] Janitor projects around core GIT
Date: Tue, 17 May 2005 11:49:10 -0400 [thread overview]
Message-ID: <8764xh26q1.fsf@coraid.com> (raw)
In-Reply-To: 4289799A.3040204@pobox.com
Jeff Garzik <jgarzik@pobox.com> writes:
> Junio C Hamano wrote:
>> * Rewrite command line parsing code, probably using GNU getopt.
>> I have three gripes about option parsing in the current code:
>
>
> Use argp. It supports short and long options, and is highly
> flexible. "info argp" should work on most Linux boxes.
Or "info libc argp" (on my debian sarge system).
--
Ed L Cashin <ecashin@coraid.com>
next prev parent reply other threads:[~2005-05-17 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 4:48 [RFH] Janitor projects around core GIT Junio C Hamano
2005-05-17 4:56 ` Jeff Garzik
2005-05-17 15:49 ` Ed L Cashin [this message]
2005-05-17 12:30 ` Name of test directory (was: [RFH] Janitor projects around core GIT) Kevin Smith
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=8764xh26q1.fsf@coraid.com \
--to=ecashin@coraid.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.