mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] Kconfig: sync with linux kernel v2.6.35-4771-g1787985
Date: Sun, 8 Aug 2010 08:48:46 +0200	[thread overview]
Message-ID: <20100808064846.GA31364@merkur.ravnborg.org> (raw)
In-Reply-To: <1281241073-19115-1-git-send-email-plagnioj@jcrosoft.com>

On Sun, Aug 08, 2010 at 06:17:53AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> this will add also the support of the new ncurse interface nconfig
> 
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>

Hi Jean-Christophe.

[jc - sorry for the duplicate.
 I forgot to delete the patch and have cancelled
 the mail to the mailing list. (too big)
]

In the kconfig land we are workng on an enhancement to
nconf so we replace the "use first or second char in  menu as hotkey".
The initial reason why we started this was that people
did not like that some menus had the second char
capitalized like this:

   "mOdule support"

The reason why "O" is capital and not "m" is that "m" hotkey
is already in use. And we use the capital letter to signal
the relevant hotkey.
menuconfig does so using a different color, but the
high level ncurses interface nconfig uses does not allow this.

We are also working on a fix to savedefconfig.
savedefconfig is a new target used to save a minimal config.

So all-in-all I would like to see this sync happen
either a bit later this kernel cycle, or that you
resync again later in this cycle.

Which bring up another question.
We have plenty of projects out there that rely
on kconfig.
What can we do to kconfig to make the integration easier?

We have discussed that kconfig should be a seperate
installable tool (as rpm, deb whatever).
But there is a few quirks needed before we can do so.

But are there any other thing we could do to
make life easier for external users?

        Sam


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2010-08-08  6:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-08  4:17 Jean-Christophe PLAGNIOL-VILLARD
2010-08-08  6:48 ` Sam Ravnborg [this message]
2010-08-08  9:06   ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-08 12:07     ` Sam Ravnborg
2010-08-08 12:20       ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-13 19:26     ` Sam Ravnborg
2010-08-14  4:35       ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-14  6:51         ` Sam Ravnborg
2010-08-09  6:49   ` Robert Schwebel
2010-08-22 12:54     ` Peter Korsgaard
2010-08-23  2:51       ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-18 15:15 ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-21 10:27   ` Sascha Hauer
2010-08-21 11:35     ` Sam Ravnborg
2010-08-22  5:07       ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-22  5:55         ` Sam Ravnborg
2010-08-22 13:48       ` Peter Korsgaard
2010-08-24 17:59       ` Uwe Kleine-König
2010-08-22  5:17 ` [PATCH v2] Kconfig: sync with linux kernel v2.6.36-rc1-168-ge36c886 Jean-Christophe PLAGNIOL-VILLARD

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=20100808064846.GA31364@merkur.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=barebox@lists.infradead.org \
    --cc=plagnioj@jcrosoft.com \
    /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