From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 49425@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#49425] [PATCH] guix-install.sh: Prompt for configuring substitutes discovery.
Date: Tue, 06 Jul 2021 16:40:06 +0200 [thread overview]
Message-ID: <87fswrqzeh.fsf_-_@gnu.org> (raw)
In-Reply-To: <86pmvv3kie.fsf@gmail.com> (zimoun's message of "Tue, 06 Jul 2021 10:38:01 +0200")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
>> diff --git a/NEWS b/NEWS
>> index b0647b3700..ad9433a921 100644
>> --- a/NEWS
>> +++ b/NEWS
>> @@ -14,7 +14,9 @@ Please send Guix bug reports to bug-guix@gnu.org.
>>
>> * Changes in 1.4.0 (since 1.3.0)
>> ** Package management
>> - * New 'deb' format for the 'guix pack' command
>> +*** New 'deb' format for the 'guix pack' command
>> +** Distribution
>> +*** The installation script can now configure substitute discovery
>>
>> * Changes in 1.3.0 (since 1.2.0)
>> ** Package management
>
>>From my point of view, this is a good practise. :-) Especially when
> preparing a new release. ;-)
>
> Now, is it a standard practise? I mean, is it asked to committers to do
> it more systematically for the changes that require it?
I think we should aim to make it standard practice!
The worst that could happen is that we’d end up with an overly detailed
‘NEWS’, but that’s probably better than the other way around.
Ludo’.
next prev parent reply other threads:[~2021-07-06 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 23:49 [bug#49425] [PATCH] guix-install.sh: Prompt for configuring substitutes discovery Maxim Cournoyer
2021-07-06 8:38 ` zimoun
2021-07-06 14:40 ` Ludovic Courtès [this message]
2021-07-06 16:16 ` Maxim Cournoyer
2021-07-06 14:44 ` Ludovic Courtès
2021-07-08 3:58 ` bug#49425: " 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
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=87fswrqzeh.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=49425@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--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 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).