From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Willy Tarreau <willy@w.ods.org>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] save kernel version in .config file
Date: Fri, 18 Jun 2004 22:02:53 -0700 [thread overview]
Message-ID: <20040618220253.6a7577f4.rddunlap@osdl.org> (raw)
In-Reply-To: <20040619040717.GA32209@alpha.home.local>
On Sat, 19 Jun 2004 06:07:17 +0200 Willy Tarreau wrote:
| On Fri, Jun 18, 2004 at 03:05:35PM -0700, Randy.Dunlap wrote:
|
| > OK, I've added date, based on Sam's comments, but someone tell me,
| > when/why does filesystem-timestamp not work for this?
|
| Oh, there may be lots of reasons. The first one which comes to my mind is
| when I archive several config files in a same directory, I rarely think
| about adding '-a' to cp to preserve the dates. And when you're experimenting
| with a kernel and you're at the 20th at the end of the day, the date in the
| config file is often more reliable than yourself to keep track of what you
| have tried.
I see.
| Thanks,
| Willy
|
| PS: do you think this could be done easily to 2.4 too ?
It's trivial for 'make menuconfig' (bash scripting) [below].
OTOH, I won't look at the tcl/tk 'xconfig' stuff...
--
~Randy
linux-2.4.26
Save kernel version and config file date in config file.
diffstat:=
scripts/Menuconfig | 5 +++++
1 files changed, 5 insertions(+)
diff -Naurp ./scripts/Menuconfig~config_version ./scripts/Menuconfig
--- ./scripts/Menuconfig~config_version 2002-08-02 17:39:46.000000000 -0700
+++ ./scripts/Menuconfig 2004-06-18 21:57:47.000000000 -0700
@@ -1275,13 +1275,18 @@ save_configuration () {
CONFIG=.tmpconfig
CONFIG_H=.tmpconfig.h
+ DATTIM=`date`
echo "#" >$CONFIG
echo "# Automatically generated by make menuconfig: don't edit" >>$CONFIG
+ echo "# Linux kernel version: $kernel_version" >>$CONFIG
+ echo "# $DATTIM" >>$CONFIG
echo "#" >>$CONFIG
echo "/*" >$CONFIG_H
echo " * Automatically generated by make menuconfig: don't edit" >>$CONFIG_H
+ echo " * Linux kernel version: $kernel_version" >>$CONFIG_H
+ echo " * $DATTIM" >>$CONFIG_H
echo " */" >>$CONFIG_H
echo "#define AUTOCONF_INCLUDED" >> $CONFIG_H
next prev parent reply other threads:[~2004-06-19 5:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 5:06 Randy.Dunlap
2004-06-18 5:34 ` Willy Tarreau
2004-06-18 20:56 ` Sam Ravnborg
2004-06-18 22:05 ` Randy.Dunlap
2004-06-18 22:30 ` Sam Ravnborg
2004-06-18 22:42 ` Roman Zippel
2004-06-18 22:43 ` Randy.Dunlap
2004-06-19 4:07 ` Willy Tarreau
2004-06-19 5:02 ` Randy.Dunlap [this message]
2004-06-19 18:34 ` Willy Tarreau
2004-06-20 4:47 ` Randy.Dunlap
2004-06-18 6:29 ` Felipe Alfaro Solana
2004-06-18 6:38 ` Paul Rolland
2004-06-18 22:04 ` Randy.Dunlap
2004-06-18 12:32 ` Jesper Juhl
2004-06-27 9:23 The Viking
2004-08-04 5:57 Randy.Dunlap
2004-08-08 19:05 ` Sam Ravnborg
2004-08-09 20:03 ` Bill Davidsen
2004-08-09 20:05 ` Randy.Dunlap
2004-08-09 20:33 ` 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=20040618220253.6a7577f4.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=willy@w.ods.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
all inboxes | Powered by JetHome®