From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] export -boot parameter as qemu_boot{0,1,2}
Date: Mon, 29 Jun 2009 18:31:25 -0400 [thread overview]
Message-ID: <1246314685.15956.42.camel@mj> (raw)
In-Reply-To: <d7ead6de0906291318v33ab2ed0l83eb1497c34180bc@mail.gmail.com>
On Mon, 2009-06-29 at 22:18 +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Mon, Jun 29, 2009 at 3:49 PM, Robert Millan<rmh@aybabtu.com> wrote:
> >> We actually agreed
> >> a while ago that they are bad, but nobody had time to remove them.
> >
> > I didn't participate in that discussion. Did Marco and Okuji agree with this?
> No. It didn't really end in a clear consesus either (partially:
> everybody agreed to remove trampolines). IMO there is nothing bad in
> nested function as long as they don't generate trampolines.
I guess it will be discussed when the patches will be posted.
In any case, there is no need for non-static nested functions in this
particular case.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-06-29 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 12:12 [PATCH] export -boot parameter as qemu_boot{0,1,2} Robert Millan
2009-06-29 4:09 ` Pavel Roskin
2009-06-29 13:49 ` Robert Millan
2009-06-29 20:18 ` Vladimir 'phcoder' Serbinenko
2009-06-29 22:31 ` Pavel Roskin [this message]
2009-06-29 22:59 ` Pavel Roskin
2009-07-01 12:58 ` 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=1246314685.15956.42.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.