From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
Subject: Re: [PATCH] enable buildable targets by default
Date: Sat, 18 Jul 2009 19:55:58 +0200 [thread overview]
Message-ID: <20090718175558.GA8867@thorin> (raw)
In-Reply-To: <1247842149.25608.44.camel@mj>
On Fri, Jul 17, 2009 at 10:49:09AM -0400, Pavel Roskin wrote:
> Once everything is compiled by default, some of the configure options
> become less meaningful, so we can consider removing them.
> [...]
> I think we should provide meaningful options. For example, an option to
> disable compiling debugging tools, or an option to add extra sanity
> checks. An option to disable efiemu64 is not meaningful for someone who
> doesn't know how to use efiemu64.
I fully agree. The idea with my proposal (we talked this on IRC, I think)
was to simplify things, so I proposed that we enable everything so we don't
have to provide flags, etc.
I prefer if we got rid of the flags, or at least most of them (lumping them
together with a flag to disable debug tools or so), and remove the summary
message as well.
--
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-18 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 13:34 [PATCH] enable buildable targets by default Vladimir 'phcoder' Serbinenko
2009-07-16 16:39 ` Vladimir 'phcoder' Serbinenko
2009-07-17 0:37 ` Pavel Roskin
[not found] ` <d7ead6de0907170221h1a204f75ucca48e46c1ff3611@mail.gmail.com>
2009-07-17 14:49 ` Pavel Roskin
2009-07-18 17:55 ` Robert Millan [this message]
[not found] ` <d7ead6de0907181141n170ec55fueb9d0dccc365cdf3@mail.gmail.com>
2009-07-18 21:38 ` Vladimir 'phcoder' Serbinenko
2009-07-18 22:54 ` Pavel Roskin
2009-07-22 17:02 ` 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=20090718175558.GA8867@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
--cc=phcoder@gmail.com \
/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.