doc: add suggestions about good practises for maintainers

Suggest how to deal with patch modifications caused by
merging or back-porting when you're a maintainer.

Signed-off-by: Willy Tarreau <w@1wt.eu>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[wking@tremily.us: removed diff context since I'm pulling out only the
D-C-O portion of SubmittingPatches]
Signed-off-by: W. Trevor King <wking@tremily.us>

We can not allow anonymous contributions to the kernel

The DCO does not mean anything if we allow anonymous contributors to the
kernel.  As this is an open source project, we need to do everything in the
open.

Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

DCO: use IANA-reserved second level domain name

Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Domen Puncer <domen@coderock.org>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Update DCO ("signoff") rules to 1.1

This adds a clause that notes explicitly that the person doing the
sign-off knows that the project (and his sign-off) is public and will
possibly get archived and re-distributed.

Start documenting the sign-off procedure in SubmittingPatches

We already have over 200 sign-off lines in the kernel, so
let's document the thing, even if discussion may still be
on-going.

[wking@tremily.us: removed diff context since I'm pulling out only the
D-C-O portion of SubmittingPatches]
Signed-off-by: W. Trevor King <wking@tremily.us>