Where to send a "patch" to scute.

Damien Goutte-Gattat dgouttegattat at incenp.org
Fri May 11 13:17:22 CEST 2018


On 05/10/2018 11:42 PM, Dirk Gottschalk via Gnupg-users wrote:
> Where shoult I send this a suggested feature?

Patches should be sent to gnupg-devel at gnupg.org, prefixing the subject 
with a "[PATCH scute]" tag. Same for feature requests.

Alternatively, you may also create a Task in the GnuPG project's bug 
tracking system at https://dev.gnupg.org/.

> Is somebody interested in this out there?

As the maintainer of Scute, I am. :)

> PS: The changes were made in some kind of dirty way, because I was in a
> hurry to get this working.

I just had a cursory look at the patch. Although I kind of like the 
idea, my main concern with it is the duplication of the entire 
src/slots.c file. I will not merge anything like that.

> If somebody has suggestions to make this in a cleaner way, feel free to comment.

Right now, my first idea would be to avoid duplicating src/slots.c and 
instead use info.grip1 or info.grip3 depending on the value of the 
ENABLE_SIGKEY flag. But I have to give it a little bit more thoughts.

In the meantime, you might want to bring the topic to the gnupg-devel 
list, which is more appropriate for development-related discussions.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20180511/c45db26d/attachment.sig>

More information about the Gnupg-users mailing list