From: "Hesse, Christian" <mail@earthworm.de>
To: "Marty Leisner" <leisner@rochester.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC -- /proc/patches to track development
Date: Thu, 16 Nov 2006 16:22:16 +0100 [thread overview]
Message-ID: <200611161622.20882.mail@earthworm.de> (raw)
In-Reply-To: <200611150117.kAF1H3CD012244@dell2.home>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
On Wednesday 15 November 2006 02:17, Marty Leisner wrote:
> 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.
I prepared such a patch [0] some time ago. It makes the file .patches in
kernel source tree available via /proc/patches.gz. Read the discussion on
lkml [1] to get more information. It still appies to actual kernels.
[0] http://www.earthworm.de/download/linux/patches.patch
[1]
http://groups.google.com/group/linux.kernel/browse_thread/thread/68497374c5870617/6cfc8eed92e9b7ff
--
Regards,
Christian
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-11-16 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 1:17 RFC -- /proc/patches to track development Marty Leisner
2006-11-15 1:46 ` Jan Engelhardt
2006-11-15 14:18 ` Erik Mouw
2006-11-16 15:22 ` Hesse, Christian [this message]
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=200611161622.20882.mail@earthworm.de \
--to=mail@earthworm.de \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.