[PATCH revised] Add gcry_mpi_ec_sub.

Markus Teich teichm at in.tum.de
Wed Oct 8 20:05:10 CEST 2014

Werner Koch wrote:
> Please send a DCO to this list (see doc/HACKING).

I did, but the mail from my non-subscribed gpg-adress was silently dropped. :/
Here it is again:

Libgcrypt Developer's Certificate of Origin.  Version 1.0

By making a contribution to the Libgcrypt 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 free software 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 free
    software 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 free software 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 free software license(s)

Signed-off-by: Markus Teich <markus dot teich at stusta dot mhn dot de>

And I have a few questions about that:
Say A certifies (a), (b) and (c), but not (d) and B certifies all four parts. If
A creates a patch, sends it to B and B publishes it, would that be a valid
contribution? What if A only meant to show the patch to B for review but not for
public sharing?
Is it ok to sign an address X with the gpg key, which only contains address Y as
I am doing right now? At least doc/HACKING does not forbid it.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: </pipermail/attachments/20141008/88b0e205/attachment.sig>

More information about the Gcrypt-devel mailing list