From: Wang YanQing <udknight@gmail.com>
To: Borislav Petkov <bp@alien8.de>,
mmarek@suse.cz, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, rdunlap@xenotime.net,
yann.morin.1998@free.fr, sakiwit@gmail.com, lacombar@gmail.com,
lucas.demarchi@profusion.mobi, dave@gnu.org,
paul.gortmaker@windriver.com, crquan@gmail.com, bpoirier@suse.de
Subject: Re: [PATCH v3]mconf: Add Save button
Date: Mon, 8 Oct 2012 16:45:44 +0800 [thread overview]
Message-ID: <20121008084544.GA1695@udknight> (raw)
In-Reply-To: <20121008082832.GB19783@liondog.tnic>
On Mon, Oct 08, 2012 at 10:28:32AM +0200, Borislav Petkov wrote:
> On Mon, Oct 08, 2012 at 03:22:49PM +0800, Wang YanQing wrote:
> > 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
>
> I understand all that, but why do you think your usecase should be
> in the kernel? I still fail to see its relevance for the majority of
> people.
No, I don't think it is only my usecase. Use fg,CRTL-Z is very normal
in terminal or in vt(console), without save button you have to exit
menuconfig every time you want to save .config.
By the way,just a quick test, qconfig, xconfig, nconfig all have the
Save button, why do them exist if we follow your opinion?
Thanks.
next prev parent reply other threads:[~2012-10-08 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 5:05 [PATCH v3]mconf: Add Save button Wang YanQing
2012-10-08 6:03 ` Borislav Petkov
2012-10-08 7:22 ` Wang YanQing
2012-10-08 8:28 ` Borislav Petkov
2012-10-08 8:45 ` Wang YanQing [this message]
2012-10-08 10:25 ` Borislav Petkov
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=20121008084544.GA1695@udknight \
--to=udknight@gmail.com \
--cc=bp@alien8.de \
--cc=bpoirier@suse.de \
--cc=crquan@gmail.com \
--cc=dave@gnu.org \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=mmarek@suse.cz \
--cc=paul.gortmaker@windriver.com \
--cc=rdunlap@xenotime.net \
--cc=sakiwit@gmail.com \
--cc=yann.morin.1998@free.fr \
/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