public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
	linux-kernel-list <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: "Make nenuconfig" does not save parameters.
Date: Sat, 10 Mar 2007 23:45:34 +0100	[thread overview]
Message-ID: <20070310224534.GA3150@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0703102234210.26332@yvahk01.tjqt.qr>

On Sat, Mar 10, 2007 at 10:34:41PM +0100, Jan Engelhardt wrote:
> 
> On Mar 10 2007 22:27, Sam Ravnborg wrote:
> >On Sat, Mar 10, 2007 at 07:23:41PM +0100, Jan Engelhardt wrote:
> >> 
> >> Whether the 'working config file path' should change when you do
> >> 'Save as Alternate' or not, is a menuconfig axiom. Ask Sam Ravnborg
> >> if you want it changed :-)
> >
> >Current behaviour is not logical but on the other hand I do not
> >see a big need to make it so.
> >It seems that people very seldom uses "save alternate" anyway.
> >
> >But patches are welcome.
> 
> ^_^ The patch has already been posted, has not it?
No.
Either we keep current behaviour or we change to the "normal"
behaviour with a "Save as..." as know from all other programs.

	Sam

  reply	other threads:[~2007-03-10 22:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-10 13:05 PROBLEM: "Make nenuconfig" does not save parameters Vladimir
2007-03-10 14:25 ` Cyrill Gorcunov
2007-03-10 16:06 ` Cyrill Gorcunov
2007-03-10 16:26   ` Jan Engelhardt
2007-03-10 16:35     ` Cyrill Gorcunov
2007-03-10 16:47       ` Jan Engelhardt
     [not found]     ` <20070310194617.2aef1006@localhost>
2007-03-10 16:50       ` Jan Engelhardt
2007-03-10 17:50         ` Cyrill Gorcunov
2007-03-10 18:23           ` Jan Engelhardt
2007-03-10 18:50             ` Cyrill Gorcunov
2007-03-10 19:04               ` Jan Engelhardt
2007-03-10 19:31                 ` Cyrill Gorcunov
2007-03-10 21:27             ` Sam Ravnborg
2007-03-10 21:34               ` Jan Engelhardt
2007-03-10 22:45                 ` Sam Ravnborg [this message]
2007-03-10 23:22                   ` Jan Engelhardt
2007-03-11  7:44                   ` Cyrill Gorcunov
2007-03-11 10:07                   ` Cyrill Gorcunov
2007-03-11 19:50                     ` Sam Ravnborg
2007-03-12  6:00                       ` Cyrill Gorcunov
2007-03-12 17:49                       ` Cyrill Gorcunov
2007-03-17 14:38                       ` Cyrill Gorcunov
2007-03-18 16:12                       ` Roman Zippel
     [not found] <7X9Ep-6Iu-1@gated-at.bofh.it>
     [not found] ` <7XcsC-2Iz-3@gated-at.bofh.it>
     [not found]   ` <7XcCq-2VQ-15@gated-at.bofh.it>
     [not found]     ` <7Xd5o-3wR-15@gated-at.bofh.it>
     [not found]       ` <7Xd5o-3wR-13@gated-at.bofh.it>
     [not found]         ` <7Xe1t-52k-11@gated-at.bofh.it>
     [not found]           ` <7XeE6-67b-1@gated-at.bofh.it>
     [not found]             ` <7XhiJ-1UJ-15@gated-at.bofh.it>
     [not found]               ` <7Xhsk-26S-9@gated-at.bofh.it>
     [not found]                 ` <7Xiy3-3MW-17@gated-at.bofh.it>
2007-03-11  5:21                   ` Bodo Eggert
2007-03-11  7:50                     ` Cyrill Gorcunov

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=20070310224534.GA3150@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=gorcunov@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --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