all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luis Felipe via Guix-patches via <guix-patches@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Timothy Sample <samplet@ngyro.com>,
	72314@debbugs.gnu.org,
	Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>,
	Vagrant Cascadian <vagrant@reproducible-builds.org>,
	Simon Tournier <zimon.toutoune@gmail.com>
Subject: [bug#72314] claims Guix can make about reproducibility (was Re: [bug#72314] [PATCH v1 1/3] website: Redesign home page.)
Date: Wed, 31 Jul 2024 16:25:48 +0000	[thread overview]
Message-ID: <fbb4f881-4911-4958-bd63-0e7cb6f40626@zoho.com> (raw)
In-Reply-To: <87r0b9d26y.fsf@pelzflorian.de>


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

El 31/07/24 a las 15:13, pelzflorian (Florian Pelz) escribió:
> Luis Felipe <sirgazil@zoho.com> writes:
>> How about linking the asterisk to the blog post instead
>> (https://guix.gnu.org/blog/2024/adventures-on-the-quest-for-long-term-reproducible-deployment/)?
> Yes, your idea would mean we only link to explanations by actually
> knowledgeable people.  Good idea.
>
> But also please reword the 50 years, probably to Simon’s “Get the same
> environment in the future”, because for some packages we do not at all
> guarantee even years later.
>
> Could you send a patch?

Done. Updated to read "Get the same environment in the future*", and the 
asterisk links to the blog post.



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

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

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

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26 21:22 [bug#72314] [PATCH 0/2] website: Redesign home page sirgazil--- via Guix-patches via
2024-07-26 21:31 ` [bug#72314] [PATCH 1/2] " sirgazil--- via Guix-patches via
2024-07-26 21:31   ` [bug#72314] [PATCH 2/2] website: Move screenshots style to the screenshots style sheet sirgazil--- via Guix-patches via
2024-07-28 14:05   ` [bug#72314] [PATCH 1/2] website: Redesign home page pelzflorian (Florian Pelz)
2024-07-29  0:55     ` Luis Felipe via Guix-patches via
2024-07-29 17:10 ` [bug#72314] [PATCH 0/3] " sirgazil--- via Guix-patches via
2024-07-29 17:17 ` [bug#72314] [PATCH v1 1/3] " sirgazil--- via Guix-patches via
2024-07-29 17:17   ` [bug#72314] [PATCH v1 2/3] website: Move screenshots style to the screenshots style sheet sirgazil--- via Guix-patches via
2024-07-29 17:17   ` [bug#72314] [PATCH v1 3/3] website: Home page template: Untabify sirgazil--- via Guix-patches via
2024-07-30 15:37   ` [bug#72314] [PATCH v1 1/3] website: Redesign home page pelzflorian (Florian Pelz)
2024-07-30 17:17     ` Luis Felipe via Guix-patches via
2024-07-30 18:08     ` pelzflorian (Florian Pelz)
2024-07-30 22:44       ` Luis Felipe via Guix-patches via
2024-07-31  6:26         ` [bug#72314] claims Guix can make about reproducibility (was Re: [bug#72314] [PATCH v1 1/3] website: Redesign home page.) pelzflorian (Florian Pelz)
2024-07-31 12:47           ` Luis Felipe via Guix-patches via
2024-07-31 15:13             ` pelzflorian (Florian Pelz)
2024-07-31 16:25               ` Luis Felipe via Guix-patches via [this message]
2024-08-01 22:53                 ` bug#72314: " pelzflorian (Florian Pelz)
2024-08-01 23:24                   ` [bug#72314] " Luis Felipe via Guix-patches via
2024-07-31 16:18 ` [bug#72314] [PATCH v2 1/3] website: Redesign home page sirgazil--- via Guix-patches via
2024-07-31 16:18   ` [bug#72314] [PATCH v2 2/3] website: Move screenshots style to the screenshots style sheet sirgazil--- via Guix-patches via
2024-07-31 16:18   ` [bug#72314] [PATCH v2 3/3] website: Home page template: Untabify sirgazil--- via Guix-patches via

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=fbb4f881-4911-4958-bd63-0e7cb6f40626@zoho.com \
    --to=guix-patches@gnu.org \
    --cc=72314@debbugs.gnu.org \
    --cc=GNUtoo@cyberdimension.org \
    --cc=pelzflorian@pelzflorian.de \
    --cc=samplet@ngyro.com \
    --cc=sirgazil@zoho.com \
    --cc=vagrant@reproducible-builds.org \
    --cc=zimon.toutoune@gmail.com \
    /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.