From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] support of hfsx ( case comparaison )
Date: Wed, 03 Jun 2009 17:23:05 -0400 [thread overview]
Message-ID: <1244064185.20653.37.camel@mj> (raw)
In-Reply-To: <1244026488.5031.2.camel@akroma.ephaone.org>
Hello!
I think the ChangeLog needs to be improved. It's immodest to claim
"complete" support for something. It's a very strong statement. It's
better to say "improve". Or better yet, let's be specific. Also please
spell check the entry. "insensitive" and "insentive" is not the same.
You want the former. Please end sentences with a period. I would
write the ChangeLog entry as:
* fs/hfsplus.c: Use case sensitive comparison for hfsx when
required by the filesystem settings.
Actually, it would be better to list the functions involved. I just
want to show how long descriptions can be improved.
I also prefer not to use any negative logic, and it's easier to get it
wrong. Humans are notoriously bad at logic. Let's have
grub_hfsplus_is_case_sensitive(). I would write it like this:
static inline int
grub_hfsplus_is_case_sensitive (struct grub_hfsplus_data *data)
{
if ((grub_be_to_cpu16 (data->volheader.magic) == GRUB_HFSPLUSX_MAGIC)
&& (data->catalog_cmp_key == GRUB_HFSPLUSX_BINARYCOMPARE))
return 1;
else
return 0;
}
No need to handle unknown magic numbers.
We may need to use a comparison table as in hfs.c, as least for the
first 256 Unicode characters, but it's a separate issue.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-06-03 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 21:52 [PATCH] support of hfsx ( case comparaison ) Michael Scherer
2009-02-07 21:02 ` Robert Millan
2009-05-03 17:19 ` Michael Scherer
2009-06-01 10:11 ` Vladimir 'phcoder' Serbinenko
2009-06-03 7:56 ` Michael Scherer
2009-06-03 9:26 ` Vladimir 'phcoder' Serbinenko
2009-06-03 10:54 ` Michael Scherer
2009-06-03 21:23 ` Pavel Roskin [this message]
2009-06-05 19:23 ` Michael Scherer
2009-06-05 19:46 ` Vladimir 'phcoder' Serbinenko
2009-06-07 2:18 ` Pavel Roskin
2009-06-07 9:10 ` Vladimir 'phcoder' Serbinenko
2009-06-07 17:40 ` Pavel Roskin
2009-06-05 21:08 ` Pavel Roskin
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=1244064185.20653.37.camel@mj \
--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.