all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: 71366@debbugs.gnu.org
Cc: "Simon Tournier" <zimon.toutoune@gmail.com>,
	"Florian Pelz" <pelzflorian@pelzflorian.de>,
	"Ludovic Courtès" <ludo@gnu.org>,
	"Matthew Trzcinski" <matt@excalamus.com>,
	"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#71366] [PATCH] doc: contributing: Mention 'guix git authenticate'.
Date: Tue,  4 Jun 2024 19:55:54 +0200	[thread overview]
Message-ID: <ee338270a7fd4e5c78985fd9be237be0bf7881a2.1717523650.git.zimon.toutoune@gmail.com> (raw)

Follow up of 73b3f941d7d911a1b2bb2bf77d37cb3a12ed4291.

* doc/contributing.texi (Applying for Commit Access): Update accordingly with
the removal of 'make authenticate'.

Change-Id: Id945c484f6265c76d4eb803369a7fbd9f797434f
---
 doc/contributing.texi | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index b8adc169d8..d7f2c0afa4 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -2713,9 +2713,12 @@ Commit Access
 To check that commits are signed with correct key, use:
 
 @example
-make authenticate
+guix git authenticate
 @end example
 
+@xref{Building from Git} for running the first authentication of a Guix
+checkout.
+
 To avoid accidentally pushing unsigned or signed with the wrong key
 commits to Savannah, make sure to configure Git according to
 @xref{Configuring Git}.

base-commit: 1d198586d8ad22af2331a40113da7cb58ddad93a
-- 
2.41.0





             reply	other threads:[~2024-06-04 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 17:55 Simon Tournier [this message]
2024-06-05  1:02 ` [bug#71366] [PATCH] doc: contributing: Mention 'guix git authenticate' Maxim Cournoyer
2024-06-24  2:54   ` Maxim Cournoyer

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=ee338270a7fd4e5c78985fd9be237be0bf7881a2.1717523650.git.zimon.toutoune@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=71366@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=matt@excalamus.com \
    --cc=maxim.cournoyer@gmail.com \
    --cc=pelzflorian@pelzflorian.de \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.