unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 70759@debbugs.gnu.org, Tomas Volf <~@wolfsden.cz>,
	guix-blog@gnu.org, Skyler Ferris <skyvine@protonmail.com>
Subject: [bug#70759] [PATCH guix-artwork] website: Add post about ‘guix git authenticate’.
Date: Sun, 05 May 2024 18:31:07 +0200	[thread overview]
Message-ID: <87zft4qkz8.fsf_-_@gnu.org> (raw)
In-Reply-To: <87jzk91zbb.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Sat, 04 May 2024 15:28:24 +0200")

Hi Florian,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

> It is all well-written.  I only notice that there are typewriter
> apostrophes like “you've” mixed with typographic apostrophes “you’d”.

Oops!  Fixed locally.

> Ludovic Courtès <ludo@gnu.org> writes:
>> +# Why you should care
>
> It is good how this lists all the concepts that are insufficient. :)
> I think the explanations suffice.

Great, I’m glad it makes sense.  There seems to be a common perception
that “there’s no problem” so if this section manages to dispel that
myth, that’s good.

> However I hesitate here:
>
>> +	 ```
>> +	 git checkout --orphan keyring
>> +	 git reset --hard
>> +	 gpg --export alice@example.org > alice.key
>> +	 …
>> +	 git add *.key
>> +	 git commit -a -m "Add committer keys."
>
> Why the -a?

Oh you’re right, it’s unnecessary.  Removed!

Thanks for the quick feedback!

Ludo’.




  reply	other threads:[~2024-05-05 16:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 20:57 [bug#70759] [PATCH guix-artwork] website: Add post about ‘guix git authenticate’ Ludovic Courtès
2024-05-04 13:28 ` pelzflorian (Florian Pelz)
2024-05-05 16:31   ` Ludovic Courtès [this message]
2024-05-06  9:39 ` Simon Tournier
2024-05-06 15:49   ` Ludovic Courtès
2024-05-06 16:26     ` Simon Tournier
2024-05-07 12:17       ` bug#70759: " Ludovic Courtès

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87zft4qkz8.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=70759@debbugs.gnu.org \
    --cc=guix-blog@gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    --cc=skyvine@protonmail.com \
    --cc=~@wolfsden.cz \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).