Developer Certificate of Origin
jussi.kivilinna at iki.fi
Mon Aug 26 17:43:20 CEST 2019
On 26.8.2019 14.19, Shawn Landden wrote:
> It does not have signatures, but Marco Villegas (who also has no signatures) will sign it when he figures out how.
The public key is enough, thanks. I meant verifying the signature of your DCO.
> 23.08.2019, 12:14, "Jussi Kivilinna" <jussi.kivilinna at iki.fi>:
>> Where I can find you public key so I have verify the signature?
>>> Developer's Certificate of Origin 1.1
>>> By making a contribution to this project (libgcrypt), 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
>>> (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.
>>> The patches I just sent are here https://github.com/shawnl/libgcrypt/tree/ppc
>>> and I sign off on them.
>>>> -----BEGIN PGP SIGNATURE-----
>>>> -----END PGP SIGNATURE-----
>>> Shawn Landden
>>> Gcrypt-devel mailing list
>>> Gcrypt-devel at gnupg.org
More information about the Gcrypt-devel