mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: The Viking <viking@flying-brick.caverock.net.nz>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: viking@flying-brick.caverock.net.nz
Subject: Re: [PATCH] save kernel version in .config file
Date: Sun, 27 Jun 2004 10:23:52 +0100	[thread overview]
Message-ID: <40DE9228.2080401@flying-brick.caverock.net.nz> (raw)



-------- Original Message --------
References: <28jXg-7Hw-3@gated-at.bofh.it> <28lmp-jo-9@gated-at.bofh.it>

On Fri, 18 Jun 2004 08:38:58 +0200 Paul Rolland wrote:

| Hello,
|
| >
| > Is this interesting to anyone besides me?
| >
| Is it also possible to have this version being displayed during
| a make config/make menuconfig/... so that we know we are reading a
| config file that may have been generated for another kernel version,
| and not yet saved ?
|
| You would have, for make menuconfig :
|
|  Linux Kernel v2.2.13 Configuration, Configuration file version 2.4.20

 >Sure, it's possible.  I just don't want to add the kitchen sink.

 >IOW, I'm not convinced that it's useful most of the time...
 >only a little bit of the time.

My two cents worth:
I'd show it if it differed in kernel version, otherwise not. If this code is 
all relatively self contained, such as all being within the menuconfig/xconfig 
code, then it won't affect the running of the kernel. And yes, it would mean a 
little more code in place, but we're waiting for keyboard strokes in this 
code, or viewing its output. It's not timing-critical.

Sorry I took so long to get to this, but I've only caught up to this point.

-- 
2,313 messages to read, 2,313 messages to read - damn, Thunderbird just 
refreshed, 2,847 messages to read, ... (ad nauseum vibrum kernel)

The Viking of the Flying Brick System

             reply	other threads:[~2004-06-27 10:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27  9:23 The Viking [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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
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

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=40DE9228.2080401@flying-brick.caverock.net.nz \
    --to=viking@flying-brick.caverock.net.nz \
    --cc=linux-kernel@vger.kernel.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®