From: Adrian Bunk <bunk@stusta.de>
To: Matt Mackall <mpm@selenic.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-tiny@selenic.com
Subject: Re: [PATCH] Make vm86 support optional
Date: Thu, 29 Dec 2005 20:06:25 +0100 [thread overview]
Message-ID: <20051229190625.GN3811@stusta.de> (raw)
In-Reply-To: <20051229184717.GY3356@waste.org>
On Thu, Dec 29, 2005 at 12:47:18PM -0600, Matt Mackall wrote:
> On Thu, Dec 29, 2005 at 05:39:00AM +0100, Adrian Bunk wrote:
> > On Wed, Dec 28, 2005 at 02:27:35PM -0600, Matt Mackall wrote:
> > >...
> > > +config VM86
> > > + depends X86
> > > + default y
> > > + bool "Enable VM86 support" if EMBEDDED
> > > + help
> > > + This option is required by programs like DOSEMU to run 16-bit legacy
> > > + code on X86 processors. It also may be needed by software like
> > > + XFree86 to initialize some video cards via BIOS. Disabling this
> > > + option saves about 6k.
> > >...
> >
> > I don't like such space statements ("about 6k") in help texts, since
> > history has shown that noone updates them when the actual size
> > changes...
>
> What would you prefer? It's important to give a relative size vs
> functionality savings so people can decide whether they want a feature
> and simply saying a little/a lot is insufficient.
I'd expect people using the "enable only if you know what you are doing"
EMBEDDED option to be able to figure out themselves how big a space
saving is (and even more important whether they can actually live
without the feature).
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2005-12-29 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-28 20:27 [PATCH] Make vm86 support optional Matt Mackall
2005-12-28 20:35 ` Roland Dreier
2005-12-29 4:39 ` Adrian Bunk
2005-12-29 18:47 ` Matt Mackall
2005-12-29 19:06 ` Adrian Bunk [this message]
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=20051229190625.GN3811@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tiny@selenic.com \
--cc=mpm@selenic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox