From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Next release?
Date: Tue, 15 Jul 2008 07:40:03 +0200 [thread overview]
Message-ID: <487C3833.50303@t-online.de> (raw)
In-Reply-To: <1216067223.28189.25.camel@dv>
Pavel Roskin wrote:
> On Mon, 2008-07-14 at 18:55 +0200, Christian Franke wrote:
>
>
>> Thanks for considering Cygwin support for the next release.
>>
>> The first (and last) grub package released in the Cygwin distribution
>> was based on grub codebase from 2008-03-26. My latest reasonably tested
>> merge is ~2 month old. If desired, I can merge & test all remaining
>> changes to current HEAD and post the patches for review soon.
>>
>
> I'm sorry, I forgot that story. It may be a more radical change than I
> expected. Anyway, let's see what remains to be done.
>
>
Here is a older diffstat:
http://lists.gnu.org/archive/html/grub-devel/2008-04/msg00013.html
The changes for util/biosdisk.c, util/getroot.c, and util/mkdevicemap.c
are already checked in.
>> BTW:
>> - Supporting "Ltext0" would not help much for Cygwin, because a linker
>> script is required due to the lack of "ld -N" support.
>>
>
> We may want to use linker scripts on all platforms for uniformity.
>
>
Yes, more flexible. And the tests for _start etc. are no longer necessary.
>> - Cygwin liblzo2* packages were released 1 week before the grub package :-)
>>
>
> That means the development package too? That's good.
>
>
Yes, liblzo2-devel too.
Christian
next prev parent reply other threads:[~2008-07-15 5:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 13:03 Next release? Pavel Roskin
2008-07-14 16:55 ` Christian Franke
2008-07-14 20:27 ` Pavel Roskin
2008-07-15 5:40 ` Christian Franke [this message]
2008-07-20 21:10 ` Christian Franke
2008-07-15 13:49 ` Robert Millan
2008-07-15 15:07 ` Patrick Georgi
2008-07-15 18:39 ` Christian Franke
2008-07-15 18:32 ` Christian Franke
2008-07-15 21:04 ` Yoshinori K. Okuji
2008-07-15 22:31 ` Pavel Roskin
2008-07-15 23:15 ` Yoshinori K. Okuji
2008-07-15 23:21 ` Pavel Roskin
2008-07-15 23:32 ` Yoshinori K. Okuji
2008-07-15 23:52 ` Pavel Roskin
2008-07-16 14:11 ` Colin D Bennett
2008-07-16 14:17 ` Javier Martín
2008-07-16 16:17 ` Pavel Roskin
2008-07-16 16:28 ` Javier Martín
2008-07-16 16:08 ` Pavel Roskin
2008-07-19 15:14 ` device.map (Re: Next release?) Robert Millan
2008-07-21 21:26 ` Pavel Roskin
2008-07-22 21:36 ` Robert Millan
2008-07-22 21:57 ` Pavel Roskin
2008-07-22 22:08 ` Robert Millan
2008-07-22 22:46 ` Pavel Roskin
2008-07-19 15:06 ` Next release? Robert Millan
2008-07-19 20:16 ` Yoshinori K. Okuji
2008-07-19 20:59 ` Robert Millan
2008-07-21 20:48 ` Pavel Roskin
2008-07-22 21:37 ` Robert Millan
2008-07-22 22:01 ` Pavel Roskin
2008-07-22 22:09 ` Robert Millan
2008-07-22 22:41 ` Pavel Roskin
2008-07-24 17:02 ` Marco Gerards
2008-07-24 17:18 ` Pavel Roskin
2008-07-24 21:47 ` Christian Franke
-- strict thread matches above, loose matches on Subject: below --
2008-07-16 0:22 chaac
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=487C3833.50303@t-online.de \
--to=christian.franke@t-online.de \
--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