unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Rodriguez <yewscion@gmail.com>
To: 53368@debbugs.gnu.org
Cc: Christopher Rodriguez <yewscion@gmail.com>
Subject: bug#53368: [PATCH] Amended wording in description of .guix-authorizations file
Date: Tue, 22 Mar 2022 22:42:26 -0400	[thread overview]
Message-ID: <20220323024226.8199-1-yewscion@gmail.com> (raw)
In-Reply-To: <99e271fa-7b0e-30f6-0613-57e7942826a3@gmail.com>

---

Sorry, got my wires crossed there for a moment. Please disregard the above;
It was meant for a different ticket. Here is a small patch for the
documentation, as requested. What do You think?

 doc/guix.texi | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index 44b0f9f1ea..f14642bf89 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -5456,7 +5456,9 @@ for Computer Scientists}} for a great overview.}  The
 @end lisp
 
 Each fingerprint is followed by optional key/value pairs, as in the
-example above.  Currently these key/value pairs are ignored.
+example above.  Currently these key/value pairs are ignored, but this
+may change in the future. The @code{version} field specifies the version
+of the @code{authorizations} file the entry was written for.
 
 This authentication rule creates a chicken-and-egg issue: how do we
 authenticate the first commit?  Related to that: how do we deal with
-- 
2.34.0





  parent reply	other threads:[~2022-03-23  2:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c6607218-fc59-ef33-c1d5-7e6b3bfdd254@gmail.com>
2022-01-19 14:40 ` bug#53368: .guix-authorizations 'version' field documentation Christopher Rodriguez
2022-01-19 15:09   ` bug#53368: Patch Christopher Rodriguez
2022-01-20 13:07   ` bug#53368: .guix-authorizations 'version' field documentation Maxime Devos
2022-01-24 14:21     ` Ludovic Courtès
2022-01-24 14:47   ` bug#53368: guix-authorizations documentation Christopher Rodriguez
2022-03-05  3:47     ` bug#53368: .guix-authorizations 'version' field documentation Maxim Cournoyer
2022-03-23  2:20   ` bug#53368: Missing needed alsa-plugins Christopher Rodriguez
2022-03-23  2:42   ` Christopher Rodriguez [this message]
2022-03-23 14:42   ` bug#53368: [PATCH v3] Added orca-lang package Christopher Rodriguez
2022-03-23 15:55     ` Maxime Devos
2022-03-23 15:57     ` Maxime Devos
2022-03-23 15:58     ` Maxime Devos
2022-03-23 16:03     ` Maxime Devos
2022-03-23 16:04     ` Maxime Devos

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=20220323024226.8199-1-yewscion@gmail.com \
    --to=yewscion@gmail.com \
    --cc=53368@debbugs.gnu.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.
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).