[PATCH gpgme]: Remove duplicate field description from gpgme_subkey_t in manual

Chandler Davis via Gnupg-devel <[email protected]> Thu, 13 Nov 2025 13:04:48 +0000

Newsgroups	gmane.comp.encryption.gpg.devel
Message-ID	<IAnpb7D6uyRhqIBj82DWCsyPhKM5V-ygPkHYzUDGGVrFFctbquV_Tex6bTN7R13Ok98VcuHJs8CMSUja1dM1-NyoL3dA79Gpj7jrxRJroW8=@chandlerdavis.cc>

Hello,

I was referred here from gnupg-users to submit a patch for the gpgme 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.

Also, I'd like to request an account for the bug tracker. My handle is "bitcrshr", full name is "Chandler Davis", and email is "[email protected]". Apologies if this is already being worked on from my previous email in the users list.

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 worthwhile for me to take a shot at creating one as I get familiarized. In the meantime, I'll dig into more general resources.

Many thanks, and have a good one!

Best,
Chandler

_______________________________________________
Gnupg-devel mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-devel

0001-doc-Remove-duplicate-is_cardkey-from-gpgme_subkey_t.patch (application/octet-stream, 1 KB)

From f3bcfcda9420f7d5afa57da957809426173fe513 Mon Sep 17 00:00:00 2001
From: Chandler Davis <[email protected]>
Date: Thu, 13 Nov 2025 06:25:42 -0500
Subject: [PATCH] (doc) Remove duplicate `is_cardkey` from `gpgme_subkey_t`

---
 doc/gpgme.texi | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/doc/gpgme.texi b/doc/gpgme.texi
index a4628378..90100979 100644
--- a/doc/gpgme.texi
+++ b/doc/gpgme.texi
@@ -3646,6 +3646,7 @@ This is true if the subkey can be used for qualified signatures
 according to local government regulations.
 
 @item unsigned int is_cardkey : 1
+@since{1.2.0}
 
 This is true if the secret key or subkey is stored on a smart card.
 
@@ -3724,11 +3725,6 @@ Note that an invalid timestamp indicates a bug in the engine.
 This is the expiration timestamp of the subkey, or 0 if the subkey
 does not expire.
 
-@item unsigned int is_cardkey : 1
-@since{1.2.0}
-
-True if the secret key is stored on a smart card.
-
 @item char *card_number
 @since{1.2.0}
 
-- 
2.50.1 (Apple Git-155)

DCO (application/octet-stream, 1.2 KB) - not displayed

signature.asc (application/pgp-signature, 343 B)