From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Bean <bean123ch@gmail.com>, "Yoshinori K. Okuji" <okuji@enbug.org>
Subject: please stop this
Date: Tue, 14 Jul 2009 19:57:52 +0200 [thread overview]
Message-ID: <20090714175752.GC10523@thorin> (raw)
In-Reply-To: <ca0f59980907140849p6948b904keace81e306b7f68d@mail.gmail.com>
On Tue, Jul 14, 2009 at 11:49:37PM +0800, Bean wrote:
> Hi,
>
> This patch implement a new object format, the advantages are:
Hi Bean,
Last time this was discussed [1], there was no consensus that we should switch
to a new object format. Furthermore, Marco had some objections:
http://lists.gnu.org/archive/html/grub-devel/2009-07/msg00101.html
and I'm growing increasingly worried about this tendency. Just about every
week we have to discuss a proposal that significantly affects core
functionality, which may later be implemented and sent as a patch no matter
what we have discussed, and if left unattended, merged in SVN, and afterwards
we and our users have and additional burden of finding new bugs and fixing
them.
I agree that we have a problem due to lack of leadership, but this is not
acceptable. Marco is busy right now (traveling), so please put this on hold
untill he's back, then we can discuss it.
Don't take me wrong, Bean I really appreciate your contribution to GRUB, but
you see it as an experimentation ground, and GRUB is not a research project.
PUPA was, but GRUB aims to be a stable bootloader.
[1] http://lists.gnu.org/archive/html/grub-devel/2009-07/msg00098.html
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-07-14 17:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 15:49 [PATCH] New object format Bean
2009-07-14 17:57 ` Robert Millan [this message]
2009-07-14 18:09 ` please stop this Pavel Roskin
2009-07-14 18:17 ` Bean
2009-07-16 15:23 ` Robert Millan
2009-07-16 16:10 ` Vladimir 'phcoder' Serbinenko
2009-07-18 18:15 ` Robert Millan
2009-07-18 18:53 ` Vladimir 'phcoder' Serbinenko
2009-07-14 21:02 ` [PATCH] New object format Bean
2009-07-19 1:52 ` Isaac Dupree
2009-07-19 10:03 ` Bean
2009-07-21 20:55 ` Bean
2009-07-22 11:12 ` Bean
2009-07-22 11:47 ` Javier Martín
2009-07-22 13:34 ` Bean
2009-07-22 13:42 ` Javier Martín
2009-07-22 14:52 ` Bean
2009-07-25 19:33 ` Bean
2009-07-27 18:41 ` Bean
2009-07-28 11:00 ` Bean
2009-07-30 14:51 ` Bean
2009-07-31 18:10 ` Bean
2009-08-05 17:59 ` Bean
2009-08-07 17:18 ` Bean
2009-08-09 19:10 ` 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=20090714175752.GC10523@thorin \
--to=rmh@aybabtu.com \
--cc=bean123ch@gmail.com \
--cc=grub-devel@gnu.org \
--cc=okuji@enbug.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.