All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Zealey <mark@zealos.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.4.13 default config
Date: Sun, 28 Oct 2001 08:42:08 +0000	[thread overview]
Message-ID: <20011028084208.A24803@itsolve.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.21.0110271847240.12381-200000@Consulate.UFP.CX> <21646.1004231366@ocs3.intra.ocs.com.au>
In-Reply-To: <21646.1004231366@ocs3.intra.ocs.com.au>; from kaos@ocs.com.au on Sun, Oct 28, 2001 at 12:09:26PM +1100

On Sun, Oct 28, 2001 at 12:09:26PM +1100, Keith Owens wrote:

> On Sat, 27 Oct 2001 18:52:23 +0100 (BST), 
> Riley Williams <root@MemAlpha.CX> wrote:
> >The enclosed patch (against the raw 2.4.13 tree) adds a `make defconfig`
> >option that configures Linux with the default options obtained by simply
> >pressing ENTER to every prompt that comes up.
> >
> >Please apply.
> 
> Please don't.  You cannot blindly reply 'y' to all new options, it will
> hang on numbers and strings, the answer has to be context sensitive.
> There is already a patch for make allyes, allno, allmod and random (but
> valid) configs in kbuild 2.5.  That patch is context sensitive and can
> easily be extended with defconfig.

Pressing enter, not 'y'. There's a difference there, 'y' says yes and enter says
to accept the default

-- 

Mark Zealey (aka JALH on irc.openprojects.net: #zealos and many more)
mark@zealos.org
mark@itsolve.co.uk

UL++++>$ G!>(GCM/GCS/GS/GM) dpu? s:-@ a16! C++++>$ P++++>+++++$ L+++>+++++$
!E---? W+++>$ N- !o? !w--- O? !M? !V? !PS !PE--@ PGP+? r++ !t---?@ !X---?
!R- b+ !tv b+ DI+ D+? G+++ e>+++++ !h++* r!-- y--

(www.geekcode.com)

  reply	other threads:[~2001-10-28  8:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-27 17:52 [PATCH] 2.4.13 default config Riley Williams
2001-10-27 18:55 ` Jeff Garzik
2001-10-27 19:07   ` Linus Torvalds
2001-10-27 22:05     ` Riley Williams
2001-10-28  1:09 ` Keith Owens
2001-10-28  8:42   ` Mark Zealey [this message]
2001-10-28 10:37   ` Riley Williams

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=20011028084208.A24803@itsolve.co.uk \
    --to=mark@zealos.org \
    --cc=linux-kernel@vger.kernel.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.