Messages in this thread |  | | | Date | Wed, 15 Nov 2006 15:18:03 +0100 | | From | Erik Mouw <> | | Subject | Re: RFC -- /proc/patches to track development |
| |
On Tue, Nov 14, 2006 at 08:17:03PM -0500, 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.
[...]
> Seems very easy and has high ROI if you need to track patched kernels > locally.
Even easier and doesn't need any kernel features or special comments: use git to track your patches, enable CONFIG_LOCALVERSION_AUTO and uname will tell you exactly what kernel you're running:
erik@kostunrix:~ > uname -r 2.6.18-gf6057327 To see what's different, just use git:
git log --no-merges v2.6.18..f6057327 | git-shortlog Erik Mouw (1): 2.6.18-rc6 config for kostunrix
Erik
-- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands - 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/
|  |