unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Rodriguez <yewscion@gmail.com>
To: 53368@debbugs.gnu.org
Subject: bug#53368: .guix-authorizations 'version' field documentation
Date: Wed, 19 Jan 2022 09:40:01 -0500	[thread overview]
Message-ID: <99e271fa-7b0e-30f6-0613-57e7942826a3@gmail.com> (raw)
In-Reply-To: <c6607218-fc59-ef33-c1d5-7e6b3bfdd254@gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 912 bytes --]

Hey all,

I've just been able to clone my authenticated personal repository for
the first time in a few weeks because I was confusing the `version`
field of `(authorizations …` to be a file version field as opposed to
the version of the API being used.

For clarity, I'm working on a patch that will edit the section of the
manual to clearly specify that this is the API version (will submit
soon). It currently has a comment in the example source that reads
"current file format version", which lead me to this mistake. Nowhere
else in the text is the `version` field mentioned.

However, as a Lisper, I feel as though the symbol itself could easily
be more descriptive by using `api-version` or something similar rather
than just a generic `version`. It would help prevent other newcomers
from going through the confusion I've just had.

What do You think?

-- 

Christopher Rodriguez

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 4067 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

       reply	other threads:[~2022-01-19 15:05 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 ` Christopher Rodriguez [this message]
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   ` bug#53368: [PATCH] Amended wording in description of .guix-authorizations file Christopher Rodriguez
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=99e271fa-7b0e-30f6-0613-57e7942826a3@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).