From: Mark H Weaver <mhw@netris.org>
To: Bengt Richter <bokr@bokr.com>
Cc: guix-devel@gnu.org, Vagrant Cascadian <vagrant@debian.org>,
Marius Bakke <mbakke@fastmail.com>
Subject: Re: Linux-libre 5.8 and beyond
Date: Tue, 11 Aug 2020 00:07:46 -0400 [thread overview]
Message-ID: <87y2mlhljm.fsf@netris.org> (raw)
Bengt Richter <bokr@bokr.com> wrote:
> BTW, how did nix get such a weird alphabet for 0-31 ?
My guess is that the weird alphabet was chosen to avoid some of the most
common letters in English text, so that when scanning build outputs for
embedded hashes, one is less likely to mistake something else (e.g. text
or some other base32/base64 encoding) as a Nix hash. The omitted
letters in Nix hashes are (e t o u), whereas (e t a o) are the most
common letters in English text. I'm not sure why they chose to omit 'u'
though, given that it's quite far down the list of most common English
letters.
Regards,
Mark
next reply other threads:[~2020-08-11 4:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 4:07 Mark H Weaver [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-09 20:15 Linux-libre 5.8 and beyond Jason Self
2020-08-13 0:39 ` Mark H Weaver
2020-08-14 13:47 ` Alexandre Oliva
2020-08-15 6:03 ` Mark H Weaver
2020-08-16 1:24 ` Mark H Weaver
2020-08-16 12:43 ` Jason Self
2020-08-16 10:54 ` Jason Self
2020-08-24 3:45 ` Alexandre Oliva
2020-08-25 4:14 ` Mark H Weaver
2020-08-25 11:12 ` Alexandre Oliva
2020-08-24 3:58 ` Alexandre Oliva
2020-08-24 4:12 ` Alexandre Oliva
2020-08-24 4:34 ` Alexandre Oliva
2020-08-24 4:42 ` Alexandre Oliva
2020-08-08 20:57 Vagrant Cascadian
2020-08-09 0:02 ` Mark H Weaver
2020-08-09 3:30 ` Mark H Weaver
2020-08-09 3:43 ` Vagrant Cascadian
2020-08-09 18:09 ` Vagrant Cascadian
2020-08-09 22:17 ` Mark H Weaver
2020-08-10 22:39 ` Bengt Richter
2020-08-11 2:37 ` Tobias Geerinckx-Rice
2020-08-09 18:49 ` Leo Famulari
2020-08-25 21:01 ` Leo Famulari
2020-08-26 3:17 ` Leo Famulari
2020-08-26 15:41 ` Katherine Cox-Buday
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=87y2mlhljm.fsf@netris.org \
--to=mhw@netris.org \
--cc=bokr@bokr.com \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
--cc=vagrant@debian.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).