From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Dale Mellor <guix-devel-0brg6a@rdmp.org>, 70247@debbugs.gnu.org
Cc: rg@raghavgururajan.name, vivien@planete-kraus.eu,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#70247] [PATCH gnome-team v2 0/4] Why not bump GTK while we're at it?
Date: Thu, 25 Apr 2024 18:36:08 +0200 [thread overview]
Message-ID: <7d990e6d54cb8f063e96ec538196de2dc62f409c.camel@gmail.com> (raw)
In-Reply-To: <ac81d2c411c0c605d51aee8996f311f1d514d25d.camel@rdmp.org>
Am Dienstag, dem 23.04.2024 um 22:39 +0100 schrieb Dale Mellor:
> This is needed to put a title on the bug in QA.guix.gnu.org/patches.
Ehh, yeah, thanks for nothing, I guess, as neither the actual patches
nor anything else appear to be correctly tracked.
I've pushed this series, and I'll shortly follow it up with an
automatic merge from master. It's high time to do something, what with
the webkit situation. Let's get CI doing its usual job and hope we can
merge back to master soon.
Cheers
PS: Never ever forget about CC!
prev parent reply other threads:[~2024-04-25 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 21:23 [bug#70247] [PATCH gnome-team 0/4] Why not bump GTK while we're at it? Liliana Marie Prikler
2024-04-06 7:32 ` [bug#70247] [PATCH gnome-team v2 1/4] gnu: graphene: Build without ARM neon Liliana Marie Prikler
2024-04-06 7:34 ` [bug#70247] [PATCH gnome-team v2 2/4] gnu: gtk: Update to 4.14.2 Liliana Marie Prikler
2024-04-20 16:19 ` Maxim Cournoyer
2024-04-19 18:59 ` [bug#70247] [PATCH gnome-team v2 3/4] gnu: webkitgtk: Update to 2.44.1 Liliana Marie Prikler
2024-04-19 18:59 ` [bug#70247] [PATCH gnome-team v2 4/4] gnu: wpewebkit: " Liliana Marie Prikler
2024-04-19 1:54 ` [bug#70247] [PATCH gnome-team 0/4] Why not bump GTK while we're at it? Maxim Cournoyer
2024-04-19 18:56 ` Liliana Marie Prikler
2024-04-20 16:20 ` Maxim Cournoyer
2024-04-23 21:39 ` [bug#70247] [PATCH gnome-team v2 " Dale Mellor
2024-04-25 16:36 ` Liliana Marie Prikler [this message]
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=7d990e6d54cb8f063e96ec538196de2dc62f409c.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=70247@debbugs.gnu.org \
--cc=guix-devel-0brg6a@rdmp.org \
--cc=maxim.cournoyer@gmail.com \
--cc=rg@raghavgururajan.name \
--cc=vivien@planete-kraus.eu \
/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.