On Fri, 19 Dec 1997, Dave Cinege wrote:
>
> Just about done with adding a new kernel feature.
>
> What is the proper procedure to submit it to Linus (or whoever) for includsion in
> future 2.0 and 2.1 kernels?
>
The procedure depends on the feature. You can either mail it direct to
Linus, or the maintainer of the code you've been hacking. For example if
you made some changes to the IDE driver you want to send it off to Mark
Lord (but not ATAPI CD-ROM or tape).
If you made changes to the IPX support you'll proberbly just want to send
it direct to Linus (it's been orphaned) and if you've written a new
driver or something like that, you will proberbly have to send it to Linus
anyway (you'll proberbly want to patch linux/MAINTAINERS too).
If it's accecpted by a maintainer, the changes generally get into the
offical tree with little interferance by Linus (he generally accepts
patches from core devlopers in there area without question).
If you go the direct route, rember that you won't (generally) get a reply
from Linus, and that if your patch dosn't appear in a coupple of releases,
you should resend it.
> BTW: is the kernel list really this dead, or are there problems with the rutgers
> mailing list? Been this slow for a few months now.... (maybe a post a day is all I'm
> averaging)
Hmm, I'm getting a loads, the .com exploder may be having problems (I
think that the .com exploder handles far more addresses than any other).
Bryn
- --
PGP Pub key http://www.gytha.demon.co.uk/pubkey.asc ID: 1024/30AF2D69
On-line, adj.: FP: FC 4E 41 9E 64 C3 AB 28 A3 5A 57 F8 CC D9 A7 B8
The idea that a human being should always be accessible to a computer.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv
Comment: Probably (spelt 'Proberbly') requires PGP version 2.6 or later ;)
iQCVAwUBNJv7f+saGi8wry1pAQEIfwP+J9/1v61+W70mhA9DzsNlujItK5/ew9Zd
9f5B4VGwbCbViyo33WTUfo+nTBdMXScsomF5b0nQguXYqElRbeod4lukXqgf5Jen
7b15kF9pAWUmtnwoTtS/nLV9T2pBnRDD86X1Std7Et+CRXuPrrWHBoLu257mfD7x
aft3xBiMJsw=
=2yRc
-----END PGP SIGNATURE-----