public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Michal Marek <mmarek@suse.cz>,
	Roman Zippel <zippel@linux-m68k.org>,
	linux-kbuild@vger.kernel.org,
	Debian kernel maintainers <debian-kernel@lists.debian.org>
Subject: Re: [PATCHv2] Kbuild: kconfig: Verbose version of --listnewconfig
Date: Sat, 04 Dec 2010 21:53:42 +0000	[thread overview]
Message-ID: <1291499622.8025.83.camel@localhost> (raw)
In-Reply-To: <AANLkTimTz=AtE6FL-+HDniWwO256yuaqEJyoPWRThYqf@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]

On Sat, 2010-12-04 at 16:14 -0500, Arnaud Lacombe wrote:
> Hi,
> 
> On Sat, Dec 4, 2010 at 4:07 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> [...]
> >> >> I would not expect to see any header if there is no new symbol(s).
> >> >> However, that might complicate the code too much. Btw, I find
> >> >> "Changes" to be misleading, is that header necessary ?
> >> >
> >> > We use this feature (or an earlier version of it) in automated kernel
> >> > builds in Debian, so we expect the output to appear in build logs and
> >> > the header makes it easier to pick out.
> >> >
> >> That's easily doable outside kconfig.
> >
> > No it isn't, as the Kconfig code must be built as part of the
> > listnewconfig target.  (Building just the code first will provoke
> > warnings about the invalid config.)
> >
> echo "#"
> echo "# Changes:"
> echo "#"
> make [...] listnewconfig
> 
> does the job, without introducing extra header others do not seem to
> want to see.

Now try that with a clean tree and an outdated config file.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2010-12-04 21:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23  4:59 [PATCH] Kbuild: kconfig: Verbose version of --listnewconfig Ben Hutchings
2010-12-03 12:23 ` Michal Marek
2010-12-04 17:10   ` [PATCHv2] " Ben Hutchings
2010-12-04 18:11     ` Arnaud Lacombe
2010-12-04 18:30       ` Ben Hutchings
2010-12-04 19:19         ` Arnaud Lacombe
2010-12-04 19:53         ` Arnaud Lacombe
2010-12-04 21:07           ` Ben Hutchings
2010-12-04 21:14             ` Arnaud Lacombe
2010-12-04 21:53               ` Ben Hutchings [this message]
2010-12-04 22:29                 ` Arnaud Lacombe
2010-12-04 21:07         ` Sam Ravnborg
2010-12-04 21:09     ` Arnaud Lacombe
2010-12-04 21:43     ` Arnaud Lacombe

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=1291499622.8025.83.camel@localhost \
    --to=ben@decadent.org.uk \
    --cc=debian-kernel@lists.debian.org \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=zippel@linux-m68k.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