From: Mike Fedyk <mfedyk@matchmail.com>
To: John Bradford <john@grabjohn.com>
Cc: hch@lst.de, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix the -test3 input config damages
Date: Fri, 22 Aug 2003 11:00:30 -0700 [thread overview]
Message-ID: <20030822180030.GI1040@matchmail.com> (raw)
In-Reply-To: <200308221757.h7MHv3uS000585@81-2-122-30.bradfords.org.uk>
On Fri, Aug 22, 2003 at 06:57:03PM +0100, John Bradford wrote:
> > Is it worth it? I see EMBEDDED as more of a "STANDARD" thing - for people
> > who don't care or know, that's a slight safety-net saying "this selects
> > the things you take for grated".
>
> I'm pretty sure that's not what it was originally intended to be, but
> rather what it seems to have become. On the other hand, your
> described usage is probably more useful to the typical user.
>
> Why not have DEVELOPER to implement the original intentions of
> EMBEDDED?
I think I like CONFIG_NONSTD_ABI better.
next prev parent reply other threads:[~2003-08-22 18:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 17:57 [PATCH] fix the -test3 input config damages John Bradford
2003-08-22 18:00 ` Mike Fedyk [this message]
2003-08-25 4:03 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2003-08-22 16:38 Christoph Hellwig
2003-08-22 16:50 ` Linus Torvalds
2003-08-22 17:05 ` Christoph Hellwig
2003-08-22 17:35 ` Linus Torvalds
2003-08-22 20:49 ` Tom Rini
2003-08-25 16:13 ` Geert Uytterhoeven
2003-08-25 18:05 ` Tom Rini
2003-08-26 8:31 ` Geert Uytterhoeven
2003-08-29 21:49 ` Geert Uytterhoeven
2003-08-22 18:14 ` James Simmons
2003-08-22 22:31 ` Vojtech Pavlik
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=20030822180030.GI1040@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=hch@lst.de \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.