From: Vivien Kraus <vivien@planete-kraus.eu>
To: Josselin Poiret <dev@jpoiret.xyz>, guix-devel@gnu.org
Subject: Re: Core-updates coordination and plans
Date: Thu, 01 Feb 2024 18:53:02 +0100 [thread overview]
Message-ID: <111a33fad5877645f7789b423db5258323c16bcb.camel@planete-kraus.eu> (raw)
In-Reply-To: <87h6itzc4a.fsf@jpoiret.xyz>
Hello,
Le mercredi 31 janvier 2024 à 17:44 +0100, Josselin Poiret a écrit :
> Also, I see that most of the patches that were requested to be merged
> into c-u (like the big pages for jemalloc) actually got pushed, are
> there any other (well-tested) ones we can go for at the same time as
> the
> glibc rebuild? I will stress that this is about *core* packages now,
> I feel that it's too late to introduce more complications and delay
> the
> update any longer.
Is it too late to ask if you could cherry-pick the commits that show up
in the d6462be6a8..b701a7018d range (from gnu: eudev: Update to 3.2.14.
to gnu: upower: Update to 1.90.2. inclusive)? We have them on gnome-
team, but maybe it would rather belong in core-updates.
What do you think?
Best regards,
Vivien
next prev parent reply other threads:[~2024-02-01 17:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 16:44 Core-updates coordination and plans Josselin Poiret
2024-01-31 18:19 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-31 21:59 ` Vivien Kraus
2024-01-31 23:28 ` Eudev in gnome-team [Was: Core-updates coordination and plans] Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-31 20:18 ` Core-updates coordination and plans Andreas Enge
2024-02-26 15:26 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-27 16:26 ` Andreas Enge
2024-02-27 17:49 ` Vagrant Cascadian
2024-02-27 20:51 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-31 22:01 ` Vagrant Cascadian
2024-02-01 17:53 ` Vivien Kraus [this message]
2024-02-18 13:51 ` Josselin Poiret
2024-02-24 16:11 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=111a33fad5877645f7789b423db5258323c16bcb.camel@planete-kraus.eu \
--to=vivien@planete-kraus.eu \
--cc=dev@jpoiret.xyz \
--cc=guix-devel@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 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.