From: Frans Pop <elendil@planet.nl>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, zippel@linux-m68k.org,
mingo@elte.hu, akpm@linux-foundation.org,
torvalds@linux-foundation.org, geert@linux-m68k.org,
cloos@jhcloos.com
Subject: Re: [PATCH] v3 kconfig: place git SHA1 in .config output if in SCM
Date: Fri, 5 Mar 2010 04:43:27 +0100 [thread overview]
Message-ID: <201003050443.30431.elendil@planet.nl> (raw)
In-Reply-To: <20100305025435.GA6836@linux.vnet.ibm.com>
On Friday 05 March 2010, Paul E. McKenney wrote:
> o Added the KBUILD_CONFIG_NO_CHECK_DIRTY environment variable,
> and modified scripts/setlocalversion to check it, as suggested
> by James Cloos.
Just to state the obvious: this will also affect CONFIG_LOCALVERSION_AUTO.
> @@ -450,12 +457,52 @@ int conf_write(const char *name)
> if (env && *env)
> use_timestamp = 0;
>
> + strcpy(localversion, "-?-nopath");
> + path = getenv(SRCTREE);
> + if (path && *path) {
> + strcpy(localversion, "-?-pipe()-failed");
> + if (pipe(pipefd) != 0)
> + goto nolocalversion;
> + env = getenv("KBUILD_CONFIG_NO_CHECK_DIRTY");
Is this line actually needed? AFAICT the variable is unused here and should
pass down through the environment to the setlocalversion script without
needing any help.
> + sprintf(cmdline, "%s/scripts/setlocalversion", path);
> + strcpy(localversion, "-?-fork()-failed");
> + pid = fork();
Do I read correctly that you're also postfixing error conditions to the
kernel version? Don't think that's a great idea TBH. Errors should be
printed to STDERR as they occur, not as pseudo version strings.
Users coming across them in config files would be very unlikely to be able
to make any sense of them. IMO, if no VCS version can be determined,
nothing should be printed.
Cheers,
FJP
next prev parent reply other threads:[~2010-03-05 3:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 2:54 [PATCH] v3 kconfig: place git SHA1 in .config output if in SCM Paul E. McKenney
2010-03-05 3:43 ` Frans Pop [this message]
2010-03-05 5:20 ` Paul E. McKenney
2010-03-05 17:18 ` Frans Pop
2010-03-05 20:10 ` Paul E. McKenney
2010-03-05 20:31 ` Frans Pop
2010-03-05 20:49 ` Paul E. McKenney
2010-03-05 6:10 ` Mike Galbraith
2010-03-05 12:57 ` Paul E. McKenney
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=201003050443.30431.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=akpm@linux-foundation.org \
--cc=cloos@jhcloos.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
--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