All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <nsnix@comcast.net>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: James Harper <james.harper@bendigoit.com.au>,
	xen-devel@lists.xensource.com
Subject: Re: RE: signed-off-by
Date: Fri, 16 Dec 2005 00:30:06 -0800	[thread overview]
Message-ID: <43A27B0E.4000102@comcast.net> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D409D72@liverpoolst.ad.cl.cam.ac.uk>

Ian Pratt wrote:
>  
> 
>>>Thanks for the patch, but please can we have a signed-off-by: line
>>>
>>
>>Just for the record, what is the significance of a 
>>'signed-off-by'? Is it something that hg generates or 
>>something that you just manually type into the email when you 
>>submit a patch?

I was just throwing up a page on submitting patches to the Xen project:

http://wiki.xensource.com/xenwiki/SubmittingXenPatches?action=show

I'd appreciate it if the Xen maintainers could take a look
and correct if needed. It has a link to the site referred
below that explains what the Developer's Certificate of Origin
is.

thanks,
Nivedita


> 
> The signed-off-by: line should be added by hand and is used to track the
> provenance of patches. Please see
> http://www.osdl.org/newsroom/press_releases/2004/2004_05_24_dco.html
> 
> Unless a patch is utterly trivial we need it signed off before we can
> accept it.
> 
> Thanks,
> Ian
> 
> 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; and
> 
> (d) In the case of each of (a), (b), or (c), 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
> indicated in the file.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 

      reply	other threads:[~2005-12-16  8:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-16  7:45 signed-off-by Ian Pratt
2005-12-16  8:30 ` Nivedita Singhvi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43A27B0E.4000102@comcast.net \
    --to=nsnix@comcast.net \
    --cc=james.harper@bendigoit.com.au \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.