* [PATCH 2.6.12 1/1] docs: updated some code docs
@ 2005-07-26 22:20 Xose Vazquez Perez
2005-07-26 22:36 ` Andrew Morton
2005-07-26 22:36 ` Randy Dunlap
0 siblings, 2 replies; 6+ messages in thread
From: Xose Vazquez Perez @ 2005-07-26 22:20 UTC (permalink / raw)
To: linux-kernel, akpm
[-- Attachment #1: Type: text/plain, Size: 58 bytes --]
Updated docs about how to write and submit patches/code.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: code_docs.diff --]
[-- Type: text/x-patch; name="code_docs.diff", Size: 6384 bytes --]
diff -Nuar old/Documentation/CodingStyle new/Documentation/CodingStyle
--- old/Documentation/CodingStyle 2005-07-26 00:10:55.000000000 +0200
+++ new/Documentation/CodingStyle 2005-07-25 23:58:37.000000000 +0200
@@ -422,10 +422,13 @@
URL: http://cm.bell-labs.com/cm/cs/tpop/
GNU manuals - where in compliance with K&R and this text - for cpp, gcc,
-gcc internals and indent, all available from http://www.gnu.org
+gcc internals and indent, all available from http://www.gnu.org/manual/
WG14 is the international standardization working group for the programming
language C, URL: http://std.dkuug.dk/JTC1/SC22/WG14/
+Kernel CodingStyle by greg@kroah.com at OLS 2002:
+http://www.kroah.com/linux/talks/ols_2002_kernel_codingstyle_talk/html/
+
--
Last updated on 16 February 2004 by a community effort on LKML.
diff -Nuar old/Documentation/SubmittingDrivers new/Documentation/SubmittingDrivers
--- old/Documentation/SubmittingDrivers 2005-07-26 00:11:01.000000000 +0200
+++ new/Documentation/SubmittingDrivers 2005-07-27 00:07:10.000000000 +0200
@@ -26,17 +26,17 @@
------------------------
Linux 2.0:
- No new drivers are accepted for this kernel tree
+ No new drivers are accepted for this kernel tree.
Linux 2.2:
+ No new drivers are accepted for this kernel tree.
+
+Linux 2.4:
If the code area has a general maintainer then please submit it to
the maintainer listed in MAINTAINERS in the kernel file. If the
maintainer does not respond or you cannot find the appropriate
- maintainer then please contact Alan Cox <alan@lxorguk.ukuu.org.uk>
-
-Linux 2.4:
- The same rules apply as 2.2. The final contact point for Linux 2.4
- submissions is Marcelo Tosatti <marcelo.tosatti@cyclades.com>.
+ maintainer then please contact Marcelo Tosatti
+ <marcelo.tosatti@cyclades.com>.
Linux 2.6:
The same rules apply as 2.4 except that you should follow linux-kernel
@@ -51,6 +51,7 @@
of exclusively GPL licensing, and if you wish the driver
to be useful to other communities such as BSD you may well
wish to release under multiple licenses.
+ See accepted licenses at include/linux/module.h
Copyright: The copyright owner must agree to use of GPL.
It's best if the submitter and copyright owner
@@ -141,5 +142,13 @@
http://kernelnewbies.org/
Linux USB project:
- http://sourceforge.net/projects/linux-usb/
+ http://linux-usb.sourceforge.net/
+
+How to NOT write kernel driver by arjanv@redhat.com
+ http://people.redhat.com/arjanv/olspaper.pdf
+
+Kernel Janitor:
+ http://janitor.kernelnewbies.org/
+--
+Last updated on 25 Jul 2005.
diff -Nuar old/Documentation/SubmittingPatches new/Documentation/SubmittingPatches
--- old/Documentation/SubmittingPatches 2005-07-26 00:11:01.000000000 +0200
+++ new/Documentation/SubmittingPatches 2005-07-27 00:03:56.000000000 +0200
@@ -35,7 +35,7 @@
To create a patch for a single file, it is often sufficient to do:
- SRCTREE= linux-2.4
+ SRCTREE= linux-2.6
MYFILE= drivers/net/mydriver.c
cd $SRCTREE
@@ -48,9 +48,9 @@
or unmodified kernel source tree, and generate a diff against your
own source tree. For example:
- MYSRC= /devel/linux-2.4
+ MYSRC= /devel/linux-2.6
- tar xvfz linux-2.4.0-test11.tar.gz
+ tar xvfz linux-2.6.0.tar.gz
mv linux linux-vanilla
wget http://www.moses.uklinux.net/patches/dontdiff
diff -uprN -X dontdiff linux-vanilla $MYSRC > /tmp/patch
@@ -77,7 +77,7 @@
http://developer.osdl.org/rddunlap/scripts/patching-scripts.tgz
Andrew Morton's patch scripts:
-http://www.zip.com.au/~akpm/linux/patches/patch-scripts-0.16
+http://www.zip.com.au/~akpm/linux/patches/
2) Describe your changes.
@@ -94,7 +94,7 @@
3) Separate your changes.
-Separate each logical change into its own patch.
+Separate each _logical changes_ into its own patch.
For example, if your changes include both bug fixes and performance
enhancements for a single driver, separate those changes into two
@@ -102,13 +102,17 @@
driver which uses that new API, separate those into two patches.
On the other hand, if you make a single change to numerous files,
-group those changes into a single patch. Thus a single logical change
-is contained within a single patch.
+group those changes into a single patch. Thus single logical changes
+are contained within a single patch.
If one patch depends on another patch in order for a change to be
complete, that is OK. Simply note "this patch depends on patch X"
in your patch description.
+If you cannot condense your patch set into a smaller set of patches,
+then only post say 15 or so at a time and wait for review and integration.
+
+
4) Select e-mail destination.
@@ -121,6 +125,8 @@
linux-kernel@vger.kernel.org. Most kernel developers monitor this
e-mail list, and can comment on your changes.
+Do not send more than 15 patches at once to the vger mailing lists!!!
+
Linus Torvalds is the final arbiter of all changes accepted into the
Linux kernel. His e-mail address is <torvalds@osdl.org>. He gets
a lot of e-mail, so typically you should do your best to -avoid- sending
@@ -153,6 +159,8 @@
Unless you have a reason NOT to do so, CC linux-kernel@vger.kernel.org.
+Do not send more than 15 patches at once to the vger mailing lists!!!
+
Other kernel developers besides Linus need to be aware of your change,
so that they may comment on it and offer code review and suggestions.
linux-kernel is the primary Linux kernel developer mailing list.
@@ -161,6 +169,9 @@
MAINTAINERS file for a mailing list that relates specifically to
your change.
+Majordomo lists of VGER.KERNEL.ORG at:
+ http://vger.kernel.org/vger-lists.html
+
Even if the maintainer did not respond in step #4, make sure to ALWAYS
copy the maintainer when you change their code.
@@ -378,3 +389,24 @@
+----------------------
+SECTION 3 - REFERENCES
+----------------------
+
+
+'The perfect patch' by akpm@osdl.org:
+ http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
+
+'Linux kernel patch submission format' by jgarzik@pobox.com:
+ http://linux.yyz.us/patch-format.html
+
+'How to piss off a kernel subsystem maintainer' by greg@kroah.com:
+ http://www.kroah.com/log/2005/03/31/
+ http://www.kroah.com/log/2005/07/08/
+
+NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people!:
+http://marc.theaimsgroup.com/?l=linux-kernel&m=112112749912944&w=2
+
+
+--
+Last updated on 25 Jul 2005.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH 2.6.12 1/1] docs: updated some code docs
2005-07-26 22:20 [PATCH 2.6.12 1/1] docs: updated some code docs Xose Vazquez Perez
@ 2005-07-26 22:36 ` Andrew Morton
2005-07-26 22:36 ` Randy Dunlap
1 sibling, 0 replies; 6+ messages in thread
From: Andrew Morton @ 2005-07-26 22:36 UTC (permalink / raw)
To: Xose Vazquez Perez; +Cc: linux-kernel
Xose Vazquez Perez <xose.vazquez@gmail.com> wrote:
>
> Updated docs about how to write and submit patches/code.
Thanks.
I'd like some words in there pointing out that "Andrew Morton's patch
scripts" are a pile of crap and people should use quilt. Could you mention
that and resend the patch?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH 2.6.12 1/1] docs: updated some code docs
2005-07-26 22:20 [PATCH 2.6.12 1/1] docs: updated some code docs Xose Vazquez Perez
2005-07-26 22:36 ` Andrew Morton
@ 2005-07-26 22:36 ` Randy Dunlap
2005-09-26 18:10 ` Xose Vazquez Perez
1 sibling, 1 reply; 6+ messages in thread
From: Randy Dunlap @ 2005-07-26 22:36 UTC (permalink / raw)
To: Xose Vazquez Perez; +Cc: linux-kernel, akpm
Xose Vazquez Perez said:
> Updated docs about how to write and submit patches/code.
>
Parts of this should conflict with a patch in -mm from a few weeks ago.
then I check and don't see it there.... hrm, wonder what happened to it.
-Separate each logical change into its own patch.
+Separate each _logical changes_ into its own patch.
change
or drop "each" and change "its own patch"
to "a single patch file."
On the other hand, if you make a single change to numerous files,
-group those changes into a single patch. Thus a single logical change
-is contained within a single patch.
+group those changes into a single patch. Thus single logical changes
+are contained within a single patch.
It's better in the original form.
+Do not send more than 15 patches at once to the vger mailing lists!!!
Only in one place, please.
--
~Randy
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH 2.6.12 1/1] docs: updated some code docs
2005-07-26 22:36 ` Randy Dunlap
@ 2005-09-26 18:10 ` Xose Vazquez Perez
2005-09-26 18:25 ` Randy.Dunlap
0 siblings, 1 reply; 6+ messages in thread
From: Xose Vazquez Perez @ 2005-09-26 18:10 UTC (permalink / raw)
To: Randy Dunlap; +Cc: linux-kernel, akpm
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
On 7/27/05, Randy Dunlap <rdunlap@xenotime.net> wrote:
> -Separate each logical change into its own patch.
> +Separate each _logical changes_ into its own patch.
> change
> or drop "each" and change "its own patch"
> to "a single patch file."
>
> On the other hand, if you make a single change to numerous files,
> -group those changes into a single patch. Thus a single logical change
> -is contained within a single patch.
> +group those changes into a single patch. Thus single logical changes
> +are contained within a single patch.
>
> It's better in the original form.
>
> +Do not send more than 15 patches at once to the vger mailing lists!!!
>
> Only in one place, please.
ok, here it goes agains somethig called "Affluent Albatross" aka 2.6.14-rc2-git5
-thanks-
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: code_docs.diff --]
[-- Type: text/x-patch; name="code_docs.diff", Size: 5749 bytes --]
diff -Nuar old/Documentation/CodingStyle new/Documentation/CodingStyle
--- old/Documentation/CodingStyle 2005-09-26 20:02:34.000000000 +0200
+++ new/Documentation/CodingStyle 2005-09-26 20:05:59.000000000 +0200
@@ -444,10 +444,13 @@
URL: http://cm.bell-labs.com/cm/cs/tpop/
GNU manuals - where in compliance with K&R and this text - for cpp, gcc,
-gcc internals and indent, all available from http://www.gnu.org
+gcc internals and indent, all available from http://www.gnu.org/manual/
WG14 is the international standardization working group for the programming
-language C, URL: http://std.dkuug.dk/JTC1/SC22/WG14/
+language C, URL: http://www.open-std.org/JTC1/SC22/WG14/
+
+Kernel CodingStyle by greg@kroah.com at OLS 2002:
+http://www.kroah.com/linux/talks/ols_2002_kernel_codingstyle_talk/html/
--
Last updated on 16 February 2004 by a community effort on LKML.
diff -Nuar old/Documentation/SubmittingDrivers new/Documentation/SubmittingDrivers
--- old/Documentation/SubmittingDrivers 2005-09-26 20:02:34.000000000 +0200
+++ new/Documentation/SubmittingDrivers 2005-09-25 22:05:56.000000000 +0200
@@ -27,18 +27,17 @@
------------------------
Linux 2.0:
- No new drivers are accepted for this kernel tree
+ No new drivers are accepted for this kernel tree.
Linux 2.2:
+ No new drivers are accepted for this kernel tree.
+
+Linux 2.4:
If the code area has a general maintainer then please submit it to
the maintainer listed in MAINTAINERS in the kernel file. If the
maintainer does not respond or you cannot find the appropriate
- maintainer then please contact the 2.2 kernel maintainer:
- Marc-Christian Petersen <m.c.p@wolk-project.de>.
-
-Linux 2.4:
- The same rules apply as 2.2. The final contact point for Linux 2.4
- submissions is Marcelo Tosatti <marcelo.tosatti@cyclades.com>.
+ maintainer then please contact Marcelo Tosatti
+ <marcelo.tosatti@cyclades.com>.
Linux 2.6:
The same rules apply as 2.4 except that you should follow linux-kernel
@@ -53,6 +52,7 @@
of exclusive GPL licensing, and if you wish the driver
to be useful to other communities such as BSD you may well
wish to release under multiple licenses.
+ See accepted licenses at include/linux/module.h
Copyright: The copyright owner must agree to use of GPL.
It's best if the submitter and copyright owner
@@ -143,5 +143,13 @@
http://kernelnewbies.org/
Linux USB project:
- http://sourceforge.net/projects/linux-usb/
+ http://linux-usb.sourceforge.net/
+
+How to NOT write kernel driver by arjanv@redhat.com
+ http://people.redhat.com/arjanv/olspaper.pdf
+
+Kernel Janitor:
+ http://janitor.kernelnewbies.org/
+--
+Last updated on 25 Sep 2005.
diff -Nuar old/Documentation/SubmittingPatches new/Documentation/SubmittingPatches
--- old/Documentation/SubmittingPatches 2005-09-26 20:02:34.000000000 +0200
+++ new/Documentation/SubmittingPatches 2005-09-26 19:59:49.000000000 +0200
@@ -78,7 +78,8 @@
http://www.xenotime.net/linux/scripts/patching-scripts-002.tar.gz
Andrew Morton's patch scripts:
-http://www.zip.com.au/~akpm/linux/patches/patch-scripts-0.20
+http://www.zip.com.au/~akpm/linux/patches/
+Instead these ones, people should use quilt ASAP (see above).
@@ -97,7 +98,7 @@
3) Separate your changes.
-Separate each logical change into its own patch.
+Separate _logical changes_ into a single patch file.
For example, if your changes include both bug fixes and performance
enhancements for a single driver, separate those changes into two
@@ -112,6 +113,10 @@
complete, that is OK. Simply note "this patch depends on patch X"
in your patch description.
+If you cannot condense your patch set into a smaller set of patches,
+then only post say 15 or so at a time and wait for review and integration.
+
+
4) Select e-mail destination.
@@ -124,6 +129,10 @@
linux-kernel@vger.kernel.org. Most kernel developers monitor this
e-mail list, and can comment on your changes.
+
+Do not send more than 15 patches at once to the vger mailing lists!!!
+
+
Linus Torvalds is the final arbiter of all changes accepted into the
Linux kernel. His e-mail address is <torvalds@osdl.org>. He gets
a lot of e-mail, so typically you should do your best to -avoid- sending
@@ -149,6 +158,9 @@
MAINTAINERS file for a mailing list that relates specifically to
your change.
+Majordomo lists of VGER.KERNEL.ORG at:
+ http://vger.kernel.org/vger-lists.html
+
If changes affect userland-kernel interfaces, please send
the MAN-PAGES maintainer (as listed in the MAINTAINERS file)
a man-pages patch, or at least a notification of the change,
@@ -302,16 +314,6 @@
-12) More references for submitting patches
-
-Andrew Morton, "The perfect patch" (tpp).
- <http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt>
-
-Jeff Garzik, "Linux kernel patch submission format."
- <http://linux.yyz.us/patch-format.html>
-
-
-
-----------------------------------
SECTION 2 - HINTS, TIPS, AND TRICKS
-----------------------------------
@@ -382,3 +384,24 @@
Don't try to anticipate nebulous future cases which may or may not
be useful: "Make it as simple as you can, and no simpler."
+
+
+----------------------
+SECTION 3 - REFERENCES
+----------------------
+
+Andrew Morton, "The perfect patch" (tpp).
+ <http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt>
+
+Jeff Garzik, "Linux kernel patch submission format."
+ <http://linux.yyz.us/patch-format.html>
+
+Greg Kroah, "How to piss off a kernel subsystem maintainer".
+ <http://www.kroah.com/log/2005/03/31/>
+ <http://www.kroah.com/log/2005/07/08/>
+
+NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people!.
+ <http://marc.theaimsgroup.com/?l=linux-kernel&m=112112749912944&w=2>
+
+--
+Last updated on 25 Sep 2005.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH 2.6.12 1/1] docs: updated some code docs
2005-09-26 18:10 ` Xose Vazquez Perez
@ 2005-09-26 18:25 ` Randy.Dunlap
2005-09-26 18:35 ` Xose Vazquez Perez
0 siblings, 1 reply; 6+ messages in thread
From: Randy.Dunlap @ 2005-09-26 18:25 UTC (permalink / raw)
To: Xose Vazquez Perez; +Cc: Randy Dunlap, linux-kernel, akpm
On Mon, 26 Sep 2005, Xose Vazquez Perez wrote:
> ok, here it goes agains somethig called "Affluent Albatross" aka 2.6.14-rc2-git5
All looks good to me except for this one line:
Andrew Morton's patch scripts:
-http://www.zip.com.au/~akpm/linux/patches/patch-scripts-0.20 +http://www.zip.com.au/~akpm/linux/patches/
+Instead these ones, people should use quilt ASAP (see above).
Make that last line something like:
Instead of these (tools | scripts), quilt is the recommended
patch management tool (see above).
--
~Randy
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH 2.6.12 1/1] docs: updated some code docs
2005-09-26 18:25 ` Randy.Dunlap
@ 2005-09-26 18:35 ` Xose Vazquez Perez
0 siblings, 0 replies; 6+ messages in thread
From: Xose Vazquez Perez @ 2005-09-26 18:35 UTC (permalink / raw)
To: Randy.Dunlap; +Cc: linux-kernel, akpm
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
On 9/26/05, Randy.Dunlap <rdunlap@xenotime.net> wrote:
> All looks good to me except for this one line:
>
> Andrew Morton's patch scripts:
> -http://www.zip.com.au/~akpm/linux/patches/patch-scripts-0.20 +http://www.zip.com.au/~akpm/linux/patches/
> +Instead these ones, people should use quilt ASAP (see above).
>
> Make that last line something like:
> Instead of these (tools | scripts), quilt is the recommended
> patch management tool (see above).
ok. here it goes again.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: code_docs.diff --]
[-- Type: text/x-patch; name="code_docs.diff", Size: 5774 bytes --]
diff -Nuar old/Documentation/CodingStyle new/Documentation/CodingStyle
--- old/Documentation/CodingStyle 2005-09-26 20:02:34.000000000 +0200
+++ new/Documentation/CodingStyle 2005-09-26 20:05:59.000000000 +0200
@@ -444,10 +444,13 @@
URL: http://cm.bell-labs.com/cm/cs/tpop/
GNU manuals - where in compliance with K&R and this text - for cpp, gcc,
-gcc internals and indent, all available from http://www.gnu.org
+gcc internals and indent, all available from http://www.gnu.org/manual/
WG14 is the international standardization working group for the programming
-language C, URL: http://std.dkuug.dk/JTC1/SC22/WG14/
+language C, URL: http://www.open-std.org/JTC1/SC22/WG14/
+
+Kernel CodingStyle by greg@kroah.com at OLS 2002:
+http://www.kroah.com/linux/talks/ols_2002_kernel_codingstyle_talk/html/
--
Last updated on 16 February 2004 by a community effort on LKML.
diff -Nuar old/Documentation/SubmittingDrivers new/Documentation/SubmittingDrivers
--- old/Documentation/SubmittingDrivers 2005-09-26 20:02:34.000000000 +0200
+++ new/Documentation/SubmittingDrivers 2005-09-25 22:05:56.000000000 +0200
@@ -27,18 +27,17 @@
------------------------
Linux 2.0:
- No new drivers are accepted for this kernel tree
+ No new drivers are accepted for this kernel tree.
Linux 2.2:
+ No new drivers are accepted for this kernel tree.
+
+Linux 2.4:
If the code area has a general maintainer then please submit it to
the maintainer listed in MAINTAINERS in the kernel file. If the
maintainer does not respond or you cannot find the appropriate
- maintainer then please contact the 2.2 kernel maintainer:
- Marc-Christian Petersen <m.c.p@wolk-project.de>.
-
-Linux 2.4:
- The same rules apply as 2.2. The final contact point for Linux 2.4
- submissions is Marcelo Tosatti <marcelo.tosatti@cyclades.com>.
+ maintainer then please contact Marcelo Tosatti
+ <marcelo.tosatti@cyclades.com>.
Linux 2.6:
The same rules apply as 2.4 except that you should follow linux-kernel
@@ -53,6 +52,7 @@
of exclusive GPL licensing, and if you wish the driver
to be useful to other communities such as BSD you may well
wish to release under multiple licenses.
+ See accepted licenses at include/linux/module.h
Copyright: The copyright owner must agree to use of GPL.
It's best if the submitter and copyright owner
@@ -143,5 +143,13 @@
http://kernelnewbies.org/
Linux USB project:
- http://sourceforge.net/projects/linux-usb/
+ http://linux-usb.sourceforge.net/
+
+How to NOT write kernel driver by arjanv@redhat.com
+ http://people.redhat.com/arjanv/olspaper.pdf
+
+Kernel Janitor:
+ http://janitor.kernelnewbies.org/
+--
+Last updated on 25 Sep 2005.
diff -Nuar old/Documentation/SubmittingPatches new/Documentation/SubmittingPatches
--- old/Documentation/SubmittingPatches 2005-09-26 20:02:34.000000000 +0200
+++ new/Documentation/SubmittingPatches 2005-09-26 20:32:02.000000000 +0200
@@ -78,7 +78,9 @@
http://www.xenotime.net/linux/scripts/patching-scripts-002.tar.gz
Andrew Morton's patch scripts:
-http://www.zip.com.au/~akpm/linux/patches/patch-scripts-0.20
+http://www.zip.com.au/~akpm/linux/patches/
+Instead of these scripts, quilt is the recommended patch management
+tool (see above).
@@ -97,7 +99,7 @@
3) Separate your changes.
-Separate each logical change into its own patch.
+Separate _logical changes_ into a single patch file.
For example, if your changes include both bug fixes and performance
enhancements for a single driver, separate those changes into two
@@ -112,6 +114,10 @@
complete, that is OK. Simply note "this patch depends on patch X"
in your patch description.
+If you cannot condense your patch set into a smaller set of patches,
+then only post say 15 or so at a time and wait for review and integration.
+
+
4) Select e-mail destination.
@@ -124,6 +130,10 @@
linux-kernel@vger.kernel.org. Most kernel developers monitor this
e-mail list, and can comment on your changes.
+
+Do not send more than 15 patches at once to the vger mailing lists!!!
+
+
Linus Torvalds is the final arbiter of all changes accepted into the
Linux kernel. His e-mail address is <torvalds@osdl.org>. He gets
a lot of e-mail, so typically you should do your best to -avoid- sending
@@ -149,6 +159,9 @@
MAINTAINERS file for a mailing list that relates specifically to
your change.
+Majordomo lists of VGER.KERNEL.ORG at:
+ http://vger.kernel.org/vger-lists.html
+
If changes affect userland-kernel interfaces, please send
the MAN-PAGES maintainer (as listed in the MAINTAINERS file)
a man-pages patch, or at least a notification of the change,
@@ -302,16 +315,6 @@
-12) More references for submitting patches
-
-Andrew Morton, "The perfect patch" (tpp).
- <http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt>
-
-Jeff Garzik, "Linux kernel patch submission format."
- <http://linux.yyz.us/patch-format.html>
-
-
-
-----------------------------------
SECTION 2 - HINTS, TIPS, AND TRICKS
-----------------------------------
@@ -382,3 +385,24 @@
Don't try to anticipate nebulous future cases which may or may not
be useful: "Make it as simple as you can, and no simpler."
+
+
+----------------------
+SECTION 3 - REFERENCES
+----------------------
+
+Andrew Morton, "The perfect patch" (tpp).
+ <http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt>
+
+Jeff Garzik, "Linux kernel patch submission format."
+ <http://linux.yyz.us/patch-format.html>
+
+Greg Kroah, "How to piss off a kernel subsystem maintainer".
+ <http://www.kroah.com/log/2005/03/31/>
+ <http://www.kroah.com/log/2005/07/08/>
+
+NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people!.
+ <http://marc.theaimsgroup.com/?l=linux-kernel&m=112112749912944&w=2>
+
+--
+Last updated on 25 Sep 2005.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2005-09-26 18:35 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-07-26 22:20 [PATCH 2.6.12 1/1] docs: updated some code docs Xose Vazquez Perez
2005-07-26 22:36 ` Andrew Morton
2005-07-26 22:36 ` Randy Dunlap
2005-09-26 18:10 ` Xose Vazquez Perez
2005-09-26 18:25 ` Randy.Dunlap
2005-09-26 18:35 ` Xose Vazquez Perez
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox