mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: kconfig-frontends-3.4.0-0 released
Date: Tue, 22 May 2012 17:19:41 -0400	[thread overview]
Message-ID: <20120522211941.GA30024@home.goodmis.org> (raw)
In-Reply-To: <201205222221.05548.yann.morin.1998@free.fr>

On Tue, May 22, 2012 at 10:21:05PM +0200, Yann E. MORIN wrote:
> Hello All!
> 
> I'm pleased to announce the release of kconfig-frontends 3.4.0-0!
> Go download it there:
>     http://ymorin.is-a-geek.org/download/kconfig-frontends/kconfig-frontends-3.4.0-0.tar.xz
>     http://ymorin.is-a-geek.org/download/kconfig-frontends/kconfig-frontends-3.4.0-0.tar.bz2
> 
> The kconfig-frontends package provides the kconfig parser, as well as all the
> kconfig frontends and utilities, packaged using the traditional autotools, so
> the kconfig infrastructure is easy to deploy, either locally or system-wide.
> 
> What's new since 3.3.0-0:
>   - all programs are intalled with the 'kconfig-' prefix by default
>   - the kconfig documentation has been added
>   - the parser's headers are isntalled into their own sub-dir
>   - some side utilities have been added from the Linux kernel tree:
>     - kconfig-diff      show differences between two .config files

I'm curious, how is this different than scripts/diffconfig ?

-- Steve

>     - kconfig-gettext   prepare catalog of options strings for L10n
>     - kconfig-merge     merge .config fragments
>     - kconfig-tweak     get and set .config optiond from the command line
> 

  reply	other threads:[~2012-05-22 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 20:21 Yann E. MORIN
2012-05-22 21:19 ` Steven Rostedt [this message]
2012-05-22 22:11   ` Yann E. MORIN
2012-05-22 22:21     ` Steven Rostedt

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=20120522211941.GA30024@home.goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®