From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Misc patches for grub2
Date: Tue, 05 Aug 2008 12:36:06 +0200 [thread overview]
Message-ID: <87wsivg355.fsf@xs4all.nl> (raw)
In-Reply-To: <ca0f59980807250938k5632157l1ab12a89d1f74bab@mail.gmail.com> (bean123ch@gmail.com's message of "Sat, 26 Jul 2008 00:38:59 +0800")
Hi,
Bean <bean123ch@gmail.com> writes:
> This is a collection of miscellaneous patches, it includes:
Please do not collect patches. Independant changes can better go into
independant patches. Mails like this are easily overseen and so are
important changes made by such patch.
> 1, move util/envblk.c to lib/envblk.c
>
> As envblk.c is used by module loadenv and tool grub-editenv, I think
> it's better to move it to lib directory.
For some reason I have some doubts about lib/. But I do not have a
better name in mind either. What does belong in there? Do you happen
to have other names in mind as a suggestion? :-)
> 2. seperate hexdump function, and move it to lib/hexdump.c
>
> hexdump module consists of two parts, one is hexdump function, the
> other is user land command. I move the hexdump function to lib, as
> it's also used in other place, for example grub-fstest.
Same here :-)
> 3. add new command crc
>
> Just like hexdump, this module is split into two parts, lib/crc.c for
> the crc function, commands/crc.c for the user land command that
> calculate the crc checksum of selected file.
If it is for users, it should go into util/
When and how is it used?
> 4. rename appleloader command to bootcamp
>
> The name appleloader may be a little confusing, bootcamp seems to be a
> better choice.
How about legacyloader or even legacy? Isn't that what it does
without actually using possibly trademarked names people are afraid of
using?
--
Marco
next prev parent reply other threads:[~2008-08-05 10:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 16:38 [PATCH] Misc patches for grub2 Bean
2008-07-25 17:19 ` Chris Knadle
2008-07-25 17:45 ` Bean
2008-07-25 18:58 ` Chris Knadle
2008-07-27 4:36 ` Pavel Roskin
2008-07-25 20:53 ` Robert Millan
2008-07-26 4:28 ` Bean
2008-07-27 4:55 ` Pavel Roskin
2008-07-27 6:00 ` Bean
2008-07-27 7:05 ` Pavel Roskin
2008-07-27 7:14 ` Bean
2008-07-27 7:20 ` Pavel Roskin
2008-07-27 7:30 ` Bean
2008-07-27 7:33 ` Pavel Roskin
2008-07-27 13:51 ` Bean
2008-08-05 10:36 ` Marco Gerards [this message]
2008-08-05 14:14 ` Bean
2008-08-05 17:30 ` Colin D Bennett
2008-08-05 20:11 ` Robert Millan
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=87wsivg355.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.