> The problem for me is "the value of what was the previous default" is > awkward; I suggest instead saying "the previous default value" there.
New patch attached, thanks. > Is this an awkward phrasing to optimize TeX typesetting? I don't know as I somehow kept the structure of the original sentence. Feel free to improve the phrasing as the important part is that the chance in default is reflected here. (A potential additional improvement could be that it is generated into that place of the documentation, so it is not forgotten next time the default is changed.) Regards, Bernhard
From 047b9ee39f5850e4ee332a766d32fe924960e7ee Mon Sep 17 00:00:00 2001 From: Bernhard Reiter <[email protected]> Date: Fri, 17 Nov 2023 16:58:53 +0100 Subject: [PATCH] doc: update default-new-key-algo to ed25519 * adust gpg.texi to mention the default for `--default-new-key-algo`, which was changed to ed25519 with ff31dde456f32950f0df6c974b4c41f1d650d68f. --- doc/gpg.texi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/gpg.texi b/doc/gpg.texi index 17de880ea..bc60c4a47 100644 --- a/doc/gpg.texi +++ b/doc/gpg.texi @@ -3775,9 +3775,9 @@ absolute date in the form YYYY-MM-DD. Defaults to "0". This option can be used to change the default algorithms for key generation. The @var{string} is similar to the arguments required for the command @option{--quick-add-key} but slightly different. For -example the current default of @code{"rsa2048/cert,sign+rsa2048/encr"} -(or @code{"rsa3072"}) can be changed to the value of what we currently -call future default, which is @code{"ed25519/cert,sign+cv25519/encr"}. +example the current default of @code{"ed25519/cert,sign+cv25519/encr"} +can be changed to the previous default: +@code{"rsa3072/cert,sign+rsa3072/encr"}. You need to consult the source code to learn the details. Note that the advanced key generation commands can always be used to specify a key algorithm directly. -- 2.30.2
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gnupg-devel mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-devel
