From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: no commit allowed under discussion
Date: Tue, 07 Apr 2009 02:42:49 +0200 [thread overview]
Message-ID: <49DAA189.7050103@gmail.com> (raw)
In-Reply-To: <200904070937.47193.okuji@enbug.org>
Yoshinori K. Okuji wrote:
> On Tuesday 07 April 2009 01:43:17 Bean wrote:
>> On Sat, Apr 4, 2009 at 8:53 PM, Bean <bean123ch@gmail.com> wrote:
>>> On Sat, Apr 4, 2009 at 5:30 PM, Yoshinori K. Okuji <okuji@enbug.org>
> wrote:
>>>> I've undone r2063, since we're still discussing how to / not to split
>>>> modules. Bean, you must respect teamwork. If you are unable to follow
>>>> such a fundamental rule, I will have to disable your permission.
>>> Hi,
>>>
>>> I thought the previous mail is about replacing grub_printf with
>>> grub_dprint, I'm ok with that. This patch has been in mail list for
>>> sometime, it is essential to get a working display in intel macs.
>> Hi,
>>
>> How about this patch ? The split is necessary as it introduces new
>> command loadbios and fakebios that uses the fake_bios_data function,
>> and it would be ugly to put them all inside linux.c.
>
> Do you have any strong reason to make loadbios and fakebios separate? I think
> the overhead is negligible.
>
this module is useful in conjunction with other loaders (multiboot, bsd,
pc_chainloader) as well
> Regards,
> Okuji
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
--
Regards
Vladimir 'phcoder' Serbinenko
next prev parent reply other threads:[~2009-04-07 0:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 9:30 no commit allowed under discussion Yoshinori K. Okuji
2009-04-04 12:53 ` Bean
2009-04-06 16:43 ` Bean
2009-04-07 0:37 ` Yoshinori K. Okuji
2009-04-07 0:42 ` phcoder [this message]
2009-04-07 5:25 ` Bean
2009-04-09 14:23 ` Peter Cros
2009-04-14 8:23 ` Drew Rosen
2009-04-14 11:17 ` Peter Cros
2009-04-14 11:48 ` Peter Cros
2009-04-09 23:26 ` Yoshinori K. Okuji
2009-04-10 15:33 ` 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=49DAA189.7050103@gmail.com \
--to=phcoder@gmail.com \
--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.