From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Update for NTFS file system driver
Date: Wed, 13 Jun 2007 20:27:04 +0200 [thread overview]
Message-ID: <87lkenyakn.fsf@xs4all.nl> (raw)
In-Reply-To: <20070610163620.GA598@ws3.vdp.com> (bean123@126.com's message of "Mon, 11 Jun 2007 00:36:20 +0800")
Bean <bean123@126.com> writes:
[...]
> Another thing I notice, the blocklist command generate messy result when
> compared to GRUB Legacy, is it supposed to be so ?
What do you mean? Can you give an example?
> BTW, is it possible for me to join the GRUB2 development term ? I really
> want to help out.
Sure, just keep on sending patches :-)
--
Marco
next prev parent reply other threads:[~2007-06-13 18:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 4:56 Update for NTFS file system driver Bean
2007-06-09 18:05 ` Marco Gerards
2007-06-10 3:42 ` Bean
2007-06-10 7:57 ` Marco Gerards
2007-06-10 9:19 ` Thomas Schwinge
2007-06-10 9:55 ` Marco Gerards
2007-06-10 12:03 ` Bean
2007-06-10 15:15 ` Robert Millan
2007-06-10 15:29 ` Marco Gerards
2007-06-10 16:36 ` Bean
2007-06-13 18:27 ` Marco Gerards [this message]
2007-06-10 10:18 ` history of fsys_ntfs.c (Re: Update for NTFS file system driver) Robert Millan
2007-06-10 10:52 ` Bean
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=87lkenyakn.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.