public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Andrew Walrond <andrew@walrond.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.5-bk menuconfig format problem
Date: Mon, 3 Mar 2003 18:53:37 +0000	[thread overview]
Message-ID: <20030303185337.A30585@infradead.org> (raw)
In-Reply-To: <20030303184906.GF6946@louise.pinerecords.com>; from szepe@pinerecords.com on Mon, Mar 03, 2003 at 07:49:06PM +0100

On Mon, Mar 03, 2003 at 07:49:06PM +0100, Tomas Szepe wrote:
> > On Mon, Mar 03, 2003 at 03:15:34PM +0000, Andrew Walrond wrote:
> > > Just done a pull and now the first entry of make menuconfig is:
> > > 
> > >   [*] Support for paging of anonymous memory
> > > 
> > > It shouldn't really be there, should it?
> > 
> > Why not?  Even if you never want to use a swapless kernel there's still
> > plenty use for it.
> 
> Andrew probably means the problem is in _where_ the entry shows up in
> menuconfig (and he's right).  I believe he didn't mean to question the
> existence of the option.

Ah, okay :)  I newer use either menuconfig nor xconfig so I can't comment
on it's placements.  If people who actually do use if feel that it's placed
wrongly feel free to submit a patch to fix it.


  reply	other threads:[~2003-03-03 18:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 15:15 2.5-bk menuconfig format problem Andrew Walrond
2003-03-03 17:58 ` Christoph Hellwig
2003-03-03 18:49   ` Tomas Szepe
2003-03-03 18:53     ` Christoph Hellwig [this message]
2003-03-03 19:11       ` Tomas Szepe
2003-03-03 19:19       ` Sam Ravnborg
2003-03-03 19:20         ` Christoph Hellwig
2003-03-03 19:22         ` Tomas Szepe
2003-03-03 19:26           ` Randy.Dunlap
2003-03-04 20:48           ` Bill Davidsen
2003-03-03 20:38   ` Andrew Walrond

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=20030303185337.A30585@infradead.org \
    --to=hch@infradead.org \
    --cc=andrew@walrond.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=szepe@pinerecords.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