Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Guillem Jover <guillem@debian.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/3] */: Say OpenPGP instead of PGP
Date: Mon, 11 May 2026 00:06:19 +0200	[thread overview]
Message-ID: <agEAmFC7e4bGBJFo@devuan> (raw)
In-Reply-To: <20260509185022.289672-2-guillem@debian.org>

[-- Attachment #1: Type: text/plain, Size: 3750 bytes --]

Hi Guillem,

On 2026-05-09T20:50:20+0200, Guillem Jover wrote:
> From: Guillem Jover <guillem@hadrons.org>
> 
> The IETF draft is called OpenPGP, where PGP is the original
> implementation from where the specification was based on. For file

I've changed the inter-sentence space to 2.
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTING.d/patches/description#n44>

> artifacts «.pgp» is the correct short term to use though, which can

And I've changed the quotes to ASCII ones ("), to avoid making the
commit messages unnecessarily unreadable for those still using for
example the C locale.

> be considered the more implementation neutral name to use.
> 
> Signed-off-by: Guillem Jover <guillem@hadrons.org>

Thanks!  I've applied the patch.


Cheers,
Alex

> ---
>  CONTRIBUTING.d/mail             | 8 ++++----
>  CONTRIBUTING.d/patches/sendmail | 2 +-
>  man/man7/suffixes.7             | 4 ++--
>  3 files changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/CONTRIBUTING.d/mail b/CONTRIBUTING.d/mail
> index f900c0a1b..84c8fbcfb 100644
> --- a/CONTRIBUTING.d/mail
> +++ b/CONTRIBUTING.d/mail
> @@ -41,18 +41,18 @@ Description
>               it, go to
>               <https://subspace.kernel.org/vger.kernel.org.html>.
>  
> -   Sign your emails with PGP
> +   Sign your emails with OpenPGP
>          We encourage that you sign all of your emails sent to the
>          mailing list, (especially) including the ones containing
> -        patches, with your PGP key.  This helps establish trust between
> +        patches, with your OpenPGP key.  This helps establish trust between
>          you and other contributors of this project, and prevent others
>          impersonating you.  If you don't have a key, it's not mandatory
>          to sign your email, but you're encouraged to create and start
> -        using a PGP key.  See also:
> +        using a OpenPGP key.  See also:
>          <https://www.gnupg.org/faq/gnupg-faq.html#use_pgpmime>
>  
>          If you use mutt(1), we recommend the following configuration for
> -        PGP:
> +        OpenPGP:
>  
>              set crypt_autosign = yes
>              set crypt_protected_headers_write = yes
> diff --git a/CONTRIBUTING.d/patches/sendmail b/CONTRIBUTING.d/patches/sendmail
> index f0a91f993..9f2c8f554 100644
> --- a/CONTRIBUTING.d/patches/sendmail
> +++ b/CONTRIBUTING.d/patches/sendmail
> @@ -32,7 +32,7 @@ Description
>  		  ├─> [PATCH v3 02] ...
>  		  └─> [PATCH v3 03] ...
>  
> -    Sign the email containing patches with PGP
> +    Sign the email containing patches with OpenPGP
>  	See <CONTRIBUTING.d/mail> for more details on signing your mail
>  	to the list.  See also <CONTRIBUTING.d/git> for instructions for
>  	configuring git-send-email(1) to use neomutt(1) as a driver.
> diff --git a/man/man7/suffixes.7 b/man/man7/suffixes.7
> index 3e17afc77..4c8b3f27a 100644
> --- a/man/man7/suffixes.7
> +++ b/man/man7/suffixes.7
> @@ -46,7 +46,7 @@ Suffix	File type
>  \&.am	\f[B]automake\f[](1) input file
>  \&.arc	\f[B]arc\f[](1) archive
>  \&.arj	\f[B]arj\f[](1) archive
> -\&.asc	PGP ASCII-armored data
> +\&.asc	OpenPGP ASCII-armored data
>  \&.asm	(GNU) assembler source file
>  \&.au	Audio sound file
>  \&.aux	LaTeX auxiliary file
> @@ -177,7 +177,7 @@ T}
>  \&.pfa	PostScript font definition files, ASCII format
>  \&.pfb	PostScript font definition files, binary format
>  \&.pgm	portable greymap format
> -\&.pgp	PGP binary data
> +\&.pgp	OpenPGP binary data
>  \&.ph	Perl header file
>  \&.php	PHP program file
>  \&.php3	PHP3 program file
> -- 
> 2.53.0
> 
> 

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-05-10 22:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-09 18:50 [PATCH 0/3] dpkg/Debian related terminology improvements/fixes Guillem Jover
2026-05-09 18:50 ` [PATCH 1/3] */: Say OpenPGP instead of PGP Guillem Jover
2026-05-10 22:06   ` Alejandro Colomar [this message]
2026-05-09 18:50 ` [PATCH 2/3] man/man7/suffixes.7: Add xz suffixes Guillem Jover
2026-05-10 22:09   ` Alejandro Colomar
2026-05-09 18:50 ` [PATCH 3/3] man/man7/suffixes.7: Clarify Debian artifacts description Guillem Jover
2026-05-10 22:10   ` Alejandro Colomar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=agEAmFC7e4bGBJFo@devuan \
    --to=alx@kernel.org \
    --cc=guillem@debian.org \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox