public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: b_adlakha@softhome.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: menuconfig
Date: Sun, 2 Feb 2003 21:14:11 +0000 (GMT)	[thread overview]
Message-ID: <200302022114.h12LEBro008887@darkstar.example.net> (raw)
In-Reply-To: <courier.3E3D87F0.00001F1B@softhome.net> from "b_adlakha@softhome.net" at Feb 02, 2003 02:04:48 PM

> why does everything have (new) after it in the ncurses based config for 
> 2.5.59? Even the old OSS sound modules are new?

It means 'new' as in 'has not been presented to the user before'.
Once you've selected the option, it is no longer displayed as new.

> And also,
> the <save configuration to alternate file> doesn't work alright...It can't 
> access anything outside the kernel sources folder saying that the location 
> does not exist... 

It works fine here, are you sure you have the relevant permissions set
correctly?

John.

  reply	other threads:[~2003-02-02 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 21:04 menuconfig b_adlakha
2003-02-02 21:14 ` John Bradford [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-23  9:41 menuconfig Miloš Soukup

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=200302022114.h12LEBro008887@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=b_adlakha@softhome.net \
    --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