[PATCH gpgme]: Remove duplicate field description from gpgme_subkey_t in manual
Werner Koch
wk at gnupg.org
Thu Nov 13 16:32:29 CET 2025
Hi!
On Thu, 13 Nov 2025 13:04, Chandler Davis said:
> docs. I've done my best to follow the guidelines in the HACKING
> document, but please let me know if there's anything I missed or
> should keep in mind for the future.
Thanks for the patch. I merely changed the "(doc) ..." to "doc: ... and
aded a line with "--" so that this change won't show up in the generated
ChangeLog.
> Also, I'd like to request an account for the bug tracker. My handle is
> "bitcrshr", full name is "Chandler Davis", and email is
Created. You should receive a password reset mail. But take care: we
are often under AI scraper siege so don't wonder when you see error
mails.
> As an aside, I'm new to contributing via mailing list and am largely
> unfamiliar with the etiquette / norms. I was wondering if there is a
> GnuPG resource for that somewhere, or if you think it would be
I don't think so. We do it like we do this for decades. Sending
patches as an attschment is just fine. If you have a larger patch and
won't to break it up into several ones, "git format-patch" has the
options to do that. However, an initial mail describing what you want
to do is a good idea.
Oh and yes: No ABI or ABI breaks - if that is required a longer
discussion will be needed.
Salam-Shalom,
Werner
--
The pioneers of a warless world are the youth that
refuse military service. - A. Einstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openpgp-digital-signature.asc
Type: application/pgp-signature
Size: 284 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20251113/1d2ea523/attachment.sig>
More information about the Gnupg-devel
mailing list