From: Randy Dunlap <rdunlap@xenotime.net>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>, Michal Marek <mmarek@suse.cz>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH 04/15] kconfig: rephrase help texts/comments not to include the package name
Date: Wed, 20 Oct 2010 20:44:36 -0700 [thread overview]
Message-ID: <20101020204436.ed41940f.rdunlap@xenotime.net> (raw)
In-Reply-To: <AANLkTi=fN94yF=EGYgOmzcETercUkn0hwVcL5_S_qHyo@mail.gmail.com>
On Wed, 20 Oct 2010 22:40:30 -0400 Arnaud Lacombe wrote:
> Hi,
>
> I'm revisiting this. Would that make sense to rename "gkc" and "qconf"
> to respectively "gconfig" and "xconfig" ? There is copyright from
> their respective author associated with each one, so that would have
> to be updated also.
I would say yes. We always refer to gconfig, xconfig, nconfig, menuconfig...
and not to gkc nor qconf.
> Thanks,
> - Arnaud
>
> On Sat, Sep 11, 2010 at 4:22 PM, Randy Dunlap <rdunlap@xenotime.net> wrote:
> > On Sat, 11 Sep 2010 11:51:11 -0400 Arnaud Lacombe wrote:
> >> diff --git a/scripts/kconfig/gconf.c b/scripts/kconfig/gconf.c
> >> index d669882..1636213 100644
> >> --- a/scripts/kconfig/gconf.c
> >> +++ b/scripts/kconfig/gconf.c
> >> @@ -671,8 +671,7 @@ void on_introduction1_activate(GtkMenuItem * menuitem, gpointer user_data)
> >> {
> >> GtkWidget *dialog;
> >> const gchar *intro_text = _(
> >> - "Welcome to gkc, the GTK+ graphical kernel configuration tool\n"
> >> - "for Linux.\n"
> >> + "Welcome to gkc, the GTK+ graphical configuration tool\n"
> >
> > Should be "gconfig". It's never been called "gkc" AFAIK.
> >
> [...]
> >> diff --git a/scripts/kconfig/qconf.cc b/scripts/kconfig/qconf.cc
> >> index a04e451..fe18f7e 100644
> >> --- a/scripts/kconfig/qconf.cc
> >> +++ b/scripts/kconfig/qconf.cc
> >> @@ -1655,7 +1655,7 @@ void ConfigMainWindow::closeEvent(QCloseEvent* e)
> >>
> >> void ConfigMainWindow::showIntro(void)
> >> {
> >> - static const QString str = _("Welcome to the qconf graphical kernel configuration tool for Linux.\n\n"
> >> + static const QString str = _("Welcome to the qconf graphical configuration tool.\n\n"
> >
> > s/qconf/xconfig/
> >
> >> "For each option, a blank box indicates the feature is disabled, a check\n"
> >> "indicates it is enabled, and a dot indicates that it is to be compiled\n"
> >> "as a module. Clicking on the box will cycle through the three states.\n\n"
> >> --
> >
> >
> > ---
> > ~Randy
> > *** Remember to use Documentation/SubmitChecklist when testing your code ***
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-10-21 3:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 15:51 [PATCH 00/15] Kconfig generalization Arnaud Lacombe
2010-09-11 15:51 ` [PATCH 01/15] kconfig: replace a `switch()' statement by a more flexible `if()' statement Arnaud Lacombe
2010-09-11 15:51 ` [PATCH 02/15] kconfig: rephrase help text not to mention the internal prefix Arnaud Lacombe
2010-09-11 15:51 ` [PATCH 03/15] kconfig: allow build-time definition of the internal config prefix Arnaud Lacombe
2010-09-11 15:51 ` [PATCH 04/15] kconfig: rephrase help texts/comments not to include the package name Arnaud Lacombe
2010-09-11 20:22 ` Randy Dunlap
2010-09-12 4:04 ` Arnaud Lacombe
2010-10-21 2:40 ` Arnaud Lacombe
2010-10-21 3:44 ` Randy Dunlap [this message]
2010-09-17 21:59 ` Michal Marek
2010-09-11 15:51 ` [PATCH 05/15] kconfig: allow PACKAGE to be defined on the compiler's command-line Arnaud Lacombe
2010-09-11 15:51 ` [PATCH 06/15] kconfig: implement the `mainmenu' directive Arnaud Lacombe
2010-09-19 9:42 ` Sam Ravnborg
2010-09-19 14:53 ` Arnaud Lacombe
2010-09-11 15:51 ` [PATCH 07/15] kconfig: add a symbol string expansion helper Arnaud Lacombe
2010-09-11 15:51 ` [PATCH 08/15] kconfig: expand by default the rootmenu's prompt Arnaud Lacombe
2010-09-11 15:57 ` Arnaud Lacombe
2010-09-11 15:51 ` [PATCH 09/15] kconfig: replace KERNELVERSION usage by the mainmenu's prompt Arnaud Lacombe
2010-09-11 16:05 ` Arnaud Lacombe
2010-09-17 22:02 ` Michal Marek
2010-09-17 22:16 ` Arnaud Lacombe
2010-09-11 15:51 ` [PATCH 10/15] kconfig: don't emit warning upon rootmenu's prompt redefinition Arnaud Lacombe
2010-09-11 15:51 ` [PATCH 11/15] kconfig: constify file name Arnaud Lacombe
2010-09-11 15:51 ` [PATCH 12/15] kconfig: use the file's name of sourced file Arnaud Lacombe
2010-09-11 15:51 ` [PATCH 13/15] kconfig: expand file names Arnaud Lacombe
2010-09-11 15:51 ` [PATCH 14/15] kconfig: regen parser Arnaud Lacombe
2010-09-17 22:10 ` Michal Marek
2010-09-11 15:51 ` [PATCH 15/15] kbuild: migrate all arch to the kconfig mainmenu upgrade Arnaud Lacombe
2010-09-12 4:12 ` [DIFF] kbuild-generic-v5 -> kbuild-generic-v6 Arnaud Lacombe
2010-09-22 17:07 ` [DIFF] kbuild-generic-v6 -> kbuild/kconfig/kbuild-generic-v7 Arnaud Lacombe
2010-09-27 21:25 ` Michal Marek
2010-09-17 22:16 ` [PATCH 00/15] Kconfig generalization Michal Marek
2010-09-19 9:50 ` Sam Ravnborg
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=20101020204436.ed41940f.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.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