Ammar Askar <[email protected]> writes: > In commit d4563201f33a ("Documentation: simplify and clarify DCO > contribution example language"), the patch submission documentation was > updated to remove the note about pseudonyms and instead simplify it to > allow "known identities". > > The process documentation still explicitly prohibits pseudonymous > contributors. This patch changes the process documentation to line up > with the submitting patches document. > > Signed-off-by: Ammar Askar <[email protected]> > --- > I ran into this page when searching for "kernel pseudonymous" and saw > that it conflicts with changes Linus made in the patch submission > document. Figured it might be worth updating. > > Documentation/process/1.Intro.rst | 12 ++++++------ > 1 file changed, 6 insertions(+), 6 deletions(-) > > diff --git a/Documentation/process/1.Intro.rst > b/Documentation/process/1.Intro.rst > index c3d0270bbfb3..25ca49f7ae4d 100644 > --- a/Documentation/process/1.Intro.rst > +++ b/Documentation/process/1.Intro.rst > @@ -251,12 +251,12 @@ there is no prospect of a migration to version 3 of the > GPL in the > foreseeable future. > > It is imperative that all code contributed to the kernel be legitimately > -free software. For that reason, code from anonymous (or pseudonymous) > -contributors will not be accepted. All contributors are required to "sign > -off" on their code, stating that the code can be distributed with the > -kernel under the GPL. Code which has not been licensed as free software by > -its owner, or which risks creating copyright-related problems for the > -kernel (such as code which derives from reverse-engineering efforts lacking > +free software. For that reason, code from contributors without a known > +identity or anonymous contributors will not be accepted. All contributors are > +required to "sign off" on their code, stating that the code can be > distributed > +with the kernel under the GPL. Code which has not been licensed as free > +software by its owner, or which risks creating copyright-related problems for > +the kernel (such as code which derives from reverse-engineering efforts > lacking > proper safeguards) cannot be contributed.
Applied, thanks. jon
