From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] hfs+ uuid
Date: Sun, 03 May 2009 12:55:32 -0400 [thread overview]
Message-ID: <1241369732.4472.27.camel@ct> (raw)
In-Reply-To: <d7ead6de0905030342s1c4b2ca6q56ef130c8f4e48e9@mail.gmail.com>
On Sun, 2009-05-03 at 12:42 +0200, Vladimir 'phcoder' Serbinenko wrote:
> This is a patch to support UUIDs on HFS+. MD5 code is copied from
> Michael Gorven's patch which is copied from libgcrypt nearly verbatim.
> Thanks for Cris for the info about how xnu expects UUID to be
I suggest that you run all new code through GNU indent. Spacing in
"32-(n)" will probably need to be fixed manually, as it's a preprocessor
directive.
Commented out call to to _gcry_burn_stack() should probably be removed.
I would prefer that we don't use #undef. Instead, the preprocessor
defines should use unique names that never need to be redefined.
Setting two environment variables is undocumented. I think rd_string
should not be needed. If you need it due to the script engine problems,
it's better to fix the script engine. At least please mark that hack as
a hack.
Perhaps we should consider adding %X support to grub_printf(). I
realize that it will increase the core slightly, but if it's just a few
bytes, we could accept it. Other modules may use it. Or maybe we could
have grub_toupper(), perhaps an inline function?
Another thing to consider is whether md5 support should be in a separate
file. It would make it possible to reuse md5 for other commands.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-05-03 16:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 10:42 [PATCH] hfs+ uuid Vladimir 'phcoder' Serbinenko
2009-05-03 16:55 ` Pavel Roskin [this message]
2009-05-04 13:08 ` Vladimir 'phcoder' Serbinenko
2009-05-04 13:22 ` Pavel Roskin
2009-05-04 15:52 ` Vladimir 'phcoder' Serbinenko
2009-06-08 20:50 ` Vladimir 'phcoder' Serbinenko
2009-06-08 20:50 ` Vladimir 'phcoder' Serbinenko
2009-06-08 22:01 ` Pavel Roskin
2009-06-10 8:17 ` Vladimir 'phcoder' Serbinenko
2009-06-12 1:11 ` Pavel Roskin
2009-06-15 23:26 ` Vladimir 'phcoder' Serbinenko
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=1241369732.4472.27.camel@ct \
--to=proski@gnu.org \
--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.