> I'd find this addition quite helpful. I have so many of my own patches
> that I apply to so many different kernels for many different servers, so
> it's currently hard to keep track.
A better way to do this is to have each patch you want identified include
a unique file, for instance "patchname.manyfds" or "patchname.ext2comp",
in the top level source dir. Then have make gather these all together and
stick their names in the kernel. When Linus adopts a set of patches, he
can simply delete all the patchname.* files as part of his distribution
build.
For extra fun, patchname.* can contain text to be appended to CREDITS.
It would be very useful if some standard method of identifying deviation
from the standard like this was available:
"My web server just killed my crew mates and now it won't open the pod bay
doors. And I think there's a bug with the AE35 driver."
"That shouldn't be happening!? What kernel do you have? Use uname -a."
"Uh, it looks like I've got 2.2.5+REDHAT."
"Oh, maybe you've just found the first bug in feature_that_didn't_make_it_
into_2.2_but_Redhat_included_anyway. Bring the system down to runlevel
1 and look in the syslog for oopses. And check for /proc/secret-mission."
"Ok, will do. BTW, do you know anything about monoliths?"
-- "Love the dolphins," she advised him. "Write by W.A.S.T.E.."
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/