From: Karsten Wiese <annabellesgarden@yahoo.de>
To: linux-kernel@vger.kernel.org
Cc: kbuild-devel@lists.sourceforge.net
Subject: [PATCH 0/4] kconfig: Only activate UI save widgets when .config changed; Take 3
Date: Wed, 18 Oct 2006 00:23:04 +0200 [thread overview]
Message-ID: <200610180023.04978.annabellesgarden@yahoo.de> (raw)
Hi
this disables the save-widgets, as long as you haven't changed anything
yet when you are in the qt/gtk -GUI after
"make xconfig" or "make gconfig".
There were no objections on kbuild-devel,
though no comments neither on "Take 3".
Should apply from 2.6.19-rc1 onwards.
Karsten
---------- Weitergeleitete Nachricht ----------
Subject: [PATCH 0/4] kconfig: Only activate UI save widgets when .config changed; Take 3
Date: Dienstag, 10. Oktober 2006 15:33
From: Karsten Wiese <annabellesgarden@yahoo.de>
To: kbuild-devel@lists.sourceforge.net
Cc: Sam Ravnborg <sam@ravnborg.org>, Roman Zippel <zippel@linux-m68k.org>
Hi
the patchset sent following up tries to implement
functionality for *config's UIs
to know a .config's change state.
to accordingly
set GUI's save-widgets sensitivity,
remind the user to save changes.
Changes in Take 3:
Use git-format-patch instead of cg-mkpatch.
No code changes.
Comments welcome.
Karsten
-------------------------------------------------------
next reply other threads:[~2006-10-17 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 22:23 Karsten Wiese [this message]
2006-10-17 22:27 ` [PATCH 1/4] New function "bool conf_get_changed(void)" Karsten Wiese
2006-10-17 22:28 ` [PATCH 2/4] Make sym_change_count static, let it be altered by 2 functions only Karsten Wiese
2006-10-17 22:30 ` [PATCH 3/4] Add "void conf_set_changed_callback(void (*fn)(void))", use it in qconf.cc Karsten Wiese
2006-10-17 22:31 ` [PATCH 4/4] Set gconf's save-widget's sensitivity according to .config's changed state Karsten Wiese
2006-12-10 8:10 ` [PATCH 0/4] kconfig: Only activate UI save widgets when .config changed; Take 3 Andrew Morton
2006-12-11 13:08 ` Karsten Wiese
2006-12-11 18:29 ` Randy Dunlap
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=200610180023.04978.annabellesgarden@yahoo.de \
--to=annabellesgarden@yahoo.de \
--cc=kbuild-devel@lists.sourceforge.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
all inboxes | Powered by JetHome®