From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [non-finalised patch] reiserfs handling
Date: Mon, 7 Jan 2008 23:54:04 +0100 [thread overview]
Message-ID: <200801072354.04757.okuji@enbug.org> (raw)
In-Reply-To: <20080107091903.GA25426@thorin>
On Monday 07 January 2008 10:19, Robert Millan wrote:
> Great! I see that you fixed the endianess issues.
>
> I'll push this to Debian sid ASAP.
I hope I have fixed all the endianness issues, but I am not sure yet. Perhaps
I need to clean up the code further.
BTW, I noticed that make distcheck didn't work. I added missing files into
DISTLIST, but it still fails, because update-grub and some related files are
not deleted after make uninstall. Maybe you know how to fix this?
Okuji
next prev parent reply other threads:[~2008-01-07 22:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 13:56 [non-finalised patch] reiserfs handling Vincent Pelletier
2007-12-25 11:51 ` Yoshinori K. Okuji
2008-01-02 22:22 ` Robert Millan
2008-01-05 10:41 ` Yoshinori K. Okuji
2008-01-06 23:00 ` Yoshinori K. Okuji
2008-01-07 5:28 ` Jeff Chua
2008-01-07 22:51 ` Yoshinori K. Okuji
2008-01-07 9:19 ` Robert Millan
2008-01-07 22:54 ` Yoshinori K. Okuji [this message]
2008-01-08 10:01 ` 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=200801072354.04757.okuji@enbug.org \
--to=okuji@enbug.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox