Signed-off-by: Stefan Tatschner <stefan@xxxxxxxxxxxxx> --- Documentation/SubmittingPatches | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 447671b..8be6ce9 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -36,7 +36,7 @@ If you do not have a repository with the current kernel source handy, use git to obtain one. You'll want to start with the mainline repository, which can be grabbed with: - git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git + git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Note, however, that you may not want to develop against the mainline tree directly. Most subsystem maintainers run their own trees and want to see @@ -291,7 +291,7 @@ sending him e-mail. If you have a patch that fixes an exploitable security bug, send that patch to security@xxxxxxxxxx. For severe bugs, a short embargo may be considered -to allow distrbutors to get the patch out to users; in such cases, +to allow distributors to get the patch out to users; in such cases, obviously, the patch should not be sent to any public lists. Patches that fix a severe bug in a released kernel should be directed @@ -310,7 +310,7 @@ 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, so that some information makes its way into the manual pages. User-space API changes should also be copied to -linux-api@xxxxxxxxxxxxxxx. +linux-api@xxxxxxxxxxxxxxx. For small patches you may want to CC the Trivial Patch Monkey trivial@xxxxxxxxxx which collects "trivial" patches. Have a look -- 2.3.0 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
