From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: 70766-done@debbugs.gnu.org
Subject: bug#70766: Request to merge "gnome-team" branch
Date: Thu, 06 Jun 2024 23:10:09 +0200 [thread overview]
Message-ID: <b4cafe8b03da4f17c281ac8f2ad93eb6108ad831.camel@gmail.com> (raw)
In-Reply-To: <87a5jx3kqt.fsf@cbaines.net>
Am Donnerstag, dem 06.06.2024 um 20:59 +0100 schrieb Christopher
Baines:
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
>
> > Am Dienstag, dem 04.06.2024 um 21:45 +0100 schrieb Christopher
> > Baines:
> > > […]
> > >
> > > I've just looked at QA again and the numbers look really good, is
> > > gnome-team now ready to push to master?
> >
> > If it looks good to you, it's good for me. Featurewise, we more or
> > less got what we want – there is a newer WebkitGTK, but we
> > shouldn't
> > let that delay upgrading our already out-of-date WebkitGTK. Shall
> > I go
> > ahead and push?
>
> Yes, please push :)
>
> I've just reconfigured my laptop with the gnome-team changes, and I
> haven't seen any issues.
Pushed as b8780f7397dd46b5e382e48db87b8648f769d738.
Thanks for the reviews
prev parent reply other threads:[~2024-06-06 21:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 6:41 [bug#70766] Request to merge "gnome-team" branch Liliana Marie Prikler
2024-05-07 17:34 ` [bug#70766] Request for merging " Liliana Marie Prikler
2024-05-08 11:56 ` Christopher Baines
2024-05-13 9:27 ` [bug#70766] Request to merge " Christopher Baines
2024-05-17 8:11 ` Christopher Baines
2024-05-19 9:37 ` Liliana Marie Prikler
2024-05-24 14:14 ` Christopher Baines
2024-05-25 14:58 ` Liliana Marie Prikler
2024-05-26 16:51 ` Christopher Baines
2024-06-04 20:45 ` Christopher Baines
2024-06-05 4:26 ` Liliana Marie Prikler
2024-06-06 19:59 ` Christopher Baines
2024-06-06 21:10 ` 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=b4cafe8b03da4f17c281ac8f2ad93eb6108ad831.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=70766-done@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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.