Date:	Fri, 6 Jul 2007 17:21:53 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"Douglas W. Jones" <jones@...uiowa.edu>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Denis Vlasenko" <vda.linux@...glemail.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] vsprintf.c: optimizing, part 2: base 10 conversion speedup, v2

On 06/07/07, Douglas W. Jones <jones@...uiowa.edu> wrote:
>
> On Jul 5, 2007, at 4:34 PM, Andrew Morton wrote:
>
> > On Thu, 5 Jul 2007 12:51:52 +0200
> > Denis Vlasenko <vda.linux@...glemail.com> wrote:
> >
> >> Using code from
> >>
> >> http://www.cs.uiowa.edu/~jones/bcd/decimal.html
> >> (with permission from the author, Douglas W. Jones)
> >
> > Neither of your patches had signed-off-by:s.  Would prefer that
> > they were
> > included please, given that we're adding stuff from someone's website.
>
> The material on my website was somewhere between pseudocode and
> code.  The web site is tutorial in nature, and what Vlasenko did
> is follow my tutorial and adapt a working chunk of code from the
> many code snippets in the tutorial.
>
> If a signoff from me is required, someone will need to tell me how,
> since I have no experience with the protocols for Linux code
> development.  I am entirely content with the current form of credit
> given to me in the code (a comment with a pointer to my web site).
>
Section 12 of Documentation/SubmittingPatches :

"
12) Sign your work

To improve tracking of who did what, especially with patches that can
percolate to their final resting place in the kernel through several
layers of maintainers, we've introduced a "sign-off" procedure on
patches that are being emailed around.

The sign-off is a simple line at the end of the explanation for the
patch, which certifies that you wrote it or otherwise have the right to
pass it on as a open-source patch.  The rules are pretty simple: if you
can certify the below:

        Developer's Certificate of Origin 1.1

        By making a contribution to this project, I certify that:

        (a) The contribution was created in whole or in part by me and I
            have the right to submit it under the open source license
            indicated in the file; or

        (b) The contribution is based upon previous work that, to the best
            of my knowledge, is covered under an appropriate open source
            license and I have the right under that license to submit that
            work with modifications, whether created in whole or in part
            by me, under the same open source license (unless I am
            permitted to submit under a different license), as indicated
            in the file; or

        (c) The contribution was provided directly to me by some other
            person who certified (a), (b) or (c) and I have not modified
            it.

        (d) I understand and agree that this project and the contribution
            are public and that a record of the contribution (including all
            personal information I submit with it, including my sign-off) is
            maintained indefinitely and may be redistributed consistent with
            this project or the open source license(s) involved.

then you just add a line saying

        Signed-off-by: Random J Developer <random@...eloper.example.org>

using your real name (sorry, no pseudonyms or anonymous contributions.)

Some people also put extra tags at the end.  They'll just be ignored for
now, but you can do this to mark internal company procedures or just
point out some special detail about the sign-off.
"


-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists