[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121008072249.GA29113@udknight>
Date: Mon, 8 Oct 2012 15:22:49 +0800
From: Wang YanQing <udknight@...il.com>
To: Borislav Petkov <bp@...en8.de>, mmarek@...e.cz,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
rdunlap@...otime.net, yann.morin.1998@...e.fr, sakiwit@...il.com,
lacombar@...il.com, lucas.demarchi@...fusion.mobi, dave@....org,
paul.gortmaker@...driver.com, crquan@...il.com, bpoirier@...e.de
Subject: Re: [PATCH v3]mconf: Add Save button
On Mon, Oct 08, 2012 at 08:03:40AM +0200, Borislav Petkov wrote:
> Well, there are a bunch of patches from Benjamin Poirier adding the
> possibility to jump to search results and you could use them to go to
> your desired submenu.
First there are two ways to save the .config in menuconfig
1:Exit menuconfig with choice the "Yes" to save .config
2:go to top menu and use the "Save an alternate Configuration File" to save .config
No matter which way you choice, it is slow and annoying to find the origin
submenu where you have interest.The bunch of patches from Benjamin make it
a little annoying, but not ignore it.Just image the situation that you have
to exit menuconfig then "make menuconfig" and search down the submenu time
by time, it is really annoying.
> > So I add "Save" button to save our time. With "Save" button, I can use
> > CRTL-Z after save config, and then use "%" or fg to resume menuconfig
> > and go on tuning.
>
> Ok, IIUC, when you put menuconfig in the background, edit .config by
> hand in the shell and then do 'fg', you need to reload the edited
> .config back otherwise you lose your changes you just did by hand.
>
> And generally speaking, why exactly do you need to edit .config by hand,
> and, at same time, do it over menuconfig? IMO, with Benjamin's patches,
> you don't need to do that anymore, right?
>
> Thanks.
It is not the first time to make me trouble with representation by my poor English,
sorry for that.I hope the below words show the really meaning that I want to give you.
With one terminal, I can do:
1: make menuconfig
2: ajust and use "Save" button to save .config
3: use CRTL-Z(konsole) to "menuconfig" run in background
3: make && test kernel
4: fg or "%1" to resume the menuconfig
With two terminal, I can do:
in first terminal
1: make menuconfig
2: ajust and use "Save" button to save .config
in second terminal
3: make && test kernel
go back the first terminal and go on tuning.
Now, you can see what the "Save" button can do,
it make there is no "exit menuconfig" or go to
the top menu when you want to save .config in
menuconfig
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists