From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Making use of argp in GRUB utilities
Date: Fri, 26 Jan 2007 17:03:22 +0100 [thread overview]
Message-ID: <871wlh6aid.fsf@xs4all.nl> (raw)
In-Reply-To: <1169813855.3386.78.camel@pluto> (Lubomir Kundrak's message of "Fri, 26 Jan 2007 13:17:35 +0100")
Lubomir Kundrak <lkundrak@redhat.com> writes:
>> I preferred that libargp would be included in our source tree so that it would
>> be used when argp is not found in a system, but I guess Marco hasn't done it
>> yet. This depends on which is more convenient for users, using an external
>> shared library, or using our own. In GRUB Legacy, I included getopt for *BSD,
>> and I got positive answers. So I feel that it would be better to include.
>
> Sound reasonable. Would it be of any use if I converted other utils to
> make use of argp in my spare time?
It seems either that Okuji doesn't care or doesn't know yet. I
personally prefer argp because it is easy to use, flexible and less
work to maintain. And like you said, less code... less code normally
means less bugs.
So it depends on Okuji what to do. If he doesn't care I would be
happy with such a patch.
--
Marco
next prev parent reply other threads:[~2007-01-26 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 11:25 [PATCH] Making use of argp in GRUB utilities Lubomir Kundrak
2007-01-25 11:34 ` Lubomir Kundrak
2007-01-26 11:58 ` Yoshinori K. Okuji
2007-01-26 12:17 ` Lubomir Kundrak
2007-01-26 16:03 ` Marco Gerards [this message]
2007-01-26 18:42 ` Yoshinori K. Okuji
2007-01-26 16:01 ` Marco Gerards
2007-01-26 18:38 ` Yoshinori K. Okuji
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=871wlh6aid.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=grub-devel@gnu.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.