mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Marty Leisner" <leisner@rochester.rr.com>
To: linux-kernel@vger.kernel.org
Subject: RFC  -- /proc/patches to track development
Date: Tue, 14 Nov 2006 20:17:03 -0500	[thread overview]
Message-ID: <200611150117.kAF1H3CD012244@dell2.home> (raw)

I always want to know WHAT I'm running (or people I'm working with
are running) rather than  "guessing" ("do you have the most current 
patch" "I think so")

I've been a proponent of capturing .config information SOMEPLACE where
you can look at it at runtime...(it took a while but its there now).


In /proc/patches there would be a series of comments (perhaps including
file, date and time) of various patches you want to monitor.  

It would be enabled by something like

in file foo.c:
PATCH_COMMENT("this enables the foo feature");


In membar.c:
PATCH_COMMENT("go to the bar on saturday");
...
PATCH_COMMENT("watch how much you drink");


and in /proc/patches:

foo.c: compiled <date> <time>:this enables the foo feature
membar.c: compiled <date> <time>:go to the bar on saturday
member.c: compiled <date> <time>:watch how much you drink

There would be a Kconfig flag whether or not to enable this (i.e.
production kernels would not need it,
hacked kernels would, it could always be there if you're willing to
increase the footprint).

Instead of looking for aberrant behavior to identify patches, you could easily
see things with cat.

Seems very easy and has high ROI if you need to track patched kernels locally.


marty



             reply	other threads:[~2006-11-15  1:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15  1:17 Marty Leisner [this message]
2006-11-15  1:46 ` Jan Engelhardt
2006-11-15 14:18 ` Erik Mouw
2006-11-16 15:22 ` Hesse, Christian

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=200611150117.kAF1H3CD012244@dell2.home \
    --to=leisner@rochester.rr.com \
    --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®