public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mauritz <oxygene@studentenbude.ath.cx>
To: linux-kernel@vger.kernel.org
Subject: Re: Configure.help in 2.5.3-pre6
Date: Wed, 30 Jan 2002 08:54:44 +0100	[thread overview]
Message-ID: <20020130075444.GA401@hydra> (raw)
In-Reply-To: <Pine.LNX.4.33.0201292147530.22800-100000@barbarella.hawaga.org.uk> <1012370595.3392.21.camel@phantasy> <a3847v$17m$1@penguin.transmeta.com>
In-Reply-To: <a3847v$17m$1@penguin.transmeta.com>

On Wed, Jan 30, 2002 at 06:35:43AM +0000, Linus Torvalds wrote:
> >config' works.  The new per-config.in config.help is here to stay.
should be more easy to maintain - should make eric more happy

> Yes. On the other hand, if there are real problems with converting
> menu/x config to multiple help-files, a short-term answer might indeed
> be just the silly "concatenate everything into the same file".
short being between now and the cml2 inclusion?

> I'd much _prefer_ to have somebody who knows menuconfug/xconfig (or just
> wants to learn).  I have a totally untested patch for menuconfig, that
> probably just works (like the regular config thing it doesn't actualy
> take _advantage_ of pairing the Config.help files up with the questions,
> but at least it should give you the help texts like it used to). 
hmm... maybe that's a good place to finally drop cml1? given that cml2
copes with that new help-format that is *hint*

patrick mauritz
(starting an old discussion again)
-- 
             I disapprove of what you say, but I will defend
                  your right to say it with all my might

  parent reply	other threads:[~2002-01-30  7:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30  5:51 Configure.help in 2.5.3-pre6 Ben Clifford
2002-01-30  6:03 ` Robert Love
2002-01-30  6:35   ` Linus Torvalds
2002-01-30  7:11     ` Robert Love
2002-01-30  8:20       ` David Lang
2002-02-07  9:24         ` Thomas Capricelli
2002-01-30  7:54     ` Patrick Mauritz [this message]
2002-01-30  8:22       ` Jeff Garzik

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=20020130075444.GA401@hydra \
    --to=oxygene@studentenbude.ath.cx \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox