lkml.org 
[lkml]   [2004]   [May]   [11]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
FromBill Davidsen <>
SubjectRe: [PATCH] [RFC] adding support for .patches and /proc/patches.gz
DateTue, 11 May 2004 14:37:13 -0400
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:03    [from the cache]
©2003-2008