From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFC] adding support for .patches and /proc/patches.gz
Date: Tue, 11 May 2004 14:37:13 -0400 [thread overview]
Message-ID: <c7r676$gvo$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <1084157289.7867.0.camel@latitude>
Jon Oberheide wrote:
> Greetings,
>
> This feature has been brought up several times before, as can be seen
> here:
> http://www.ussg.iu.edu/hypermail/linux/kernel/0404.3/0798.html
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0203.1/0598.html
> http://www.uwsg.iu.edu/hypermail/linux/kernel/9803.0/0223.html
>
> For those unfamiliar, a file linux/.patches would be adding to the
> source tree. When applying patches to the source tree, descriptive
> information would be written to .patches. After compilation and running
> of this kernel, the .patches information would be accessible through
> /proc/patches.gz; similar to the /proc/config.gz feature.
The first question would be, patches between the current kernel and
what? Vendor kernel, people may not have it. Kernel.org kernal, just the
patches to a current vendor kernel diff would be pretty huge in some cases.
Let's say it looks like a high cost/benefit ratio, would be much less
effective unless it were used for every patch, and feels like something
you might want to do within an organization rather than as a general
practice.
Sorry, you asked for comments...
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2004-05-11 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 2:48 [PATCH] [RFC] adding support for .patches and /proc/patches.gz Jon Oberheide
2004-05-10 18:37 ` Paul Eggert
2004-05-10 18:51 ` viro
2004-05-11 9:34 ` Jan-Benedict Glaw
2004-05-11 18:37 ` Bill Davidsen [this message]
2004-05-12 4:59 ` Jon Oberheide
2004-05-12 8:28 ` Cef (LKML)
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='c7r676$gvo$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.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