From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 75026@debbugs.gnu.org
Subject: [bug#75026] [PATCH core-updates 0/7] Update gnutls and curl.
Date: Tue, 24 Dec 2024 11:15:11 +0900 [thread overview]
Message-ID: <87ikr9vnbk.fsf@gmail.com> (raw)
In-Reply-To: <87wmfq5glc.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 23 Dec 2024 20:45:03 +0100")
Hi Ludovic,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi Maxim,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> gnu: gnutls: Update to 3.8.8.
>> gnu: gnutls: Enable zstd compression.
>> gnu: gnutls: Streamline mips64el conditionals.
>> gnu: brotli: Update to 1.1.0.
>> gnu: libidn: Update to 1.42.
>> gnu: curl: Update to 8.11.1 and ungraft.
>> gnu: curl: Enable zstd support.
>
> ‘core-updates’ is now gone:
>
> https://lists.gnu.org/archive/html/guix-devel/2024-08/msg00195.html
I'm (finally) aware of this :-). But it seemed like useful, when
submitting to the trackr for review to have a subject prefix anyway to
communicate that this causes a mass rebuild, hopefully avoiding the
situation of another committer picking these up and pushing them to the
master.
> Instead, this should go on a dedicated branch, with a “request to merge”
> and a jobset on ci.guix (ideally qa.guix would pick it up but it’s
> currently out of order).
Understood; do the patches LGTY?
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-12-24 2:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 15:52 [bug#75026] [PATCH core-updates 0/7] Update gnutls and curl Maxim Cournoyer
2024-12-22 16:00 ` [bug#75026] [PATCH core-updates 1/7] gnu: gnutls: Update to 3.8.8 Maxim Cournoyer
2024-12-24 14:50 ` Ludovic Courtès
2024-12-22 16:01 ` [bug#75026] [PATCH core-updates 2/7] gnu: gnutls: Enable zstd compression Maxim Cournoyer
2024-12-22 16:01 ` [bug#75026] [PATCH core-updates 3/7] gnu: gnutls: Streamline mips64el conditionals Maxim Cournoyer
2024-12-22 16:01 ` [bug#75026] [PATCH core-updates 4/7] gnu: brotli: Update to 1.1.0 Maxim Cournoyer
2024-12-22 16:01 ` [bug#75026] [PATCH core-updates 5/7] gnu: libidn: Update to 1.42 Maxim Cournoyer
2024-12-22 16:01 ` [bug#75026] [PATCH core-updates 6/7] gnu: curl: Update to 8.11.1 and ungraft Maxim Cournoyer
2024-12-22 16:01 ` [bug#75026] [PATCH core-updates 7/7] gnu: curl: Enable zstd support Maxim Cournoyer
2024-12-23 19:45 ` [bug#75026] [PATCH core-updates 0/7] Update gnutls and curl Ludovic Courtès
2024-12-24 2:15 ` Maxim Cournoyer [this message]
2024-12-24 14:52 ` Ludovic Courtès
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=87ikr9vnbk.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=75026@debbugs.gnu.org \
--cc=ludo@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).