From: Vivien Kraus via Guix-patches via <guix-patches@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
69256@debbugs.gnu.org,
John Kehayias <john.kehayias@protonmail.com>
Cc: rg@raghavgururajan.name, maxim.cournoyer@gmail.com
Subject: [bug#69256] [PATCH gnome-team] gnu: glibmm-2.64: Rename and update to 2.66.6.
Date: Thu, 22 Feb 2024 06:43:29 +0100 [thread overview]
Message-ID: <cc649234b373816328b6b9f2abde60ff20f4c857.camel@planete-kraus.eu> (raw)
In-Reply-To: <46e9632615ee2eda61f99550a1996da4e66b4794.camel@gmail.com>
Hello!
Le jeudi 22 février 2024 à 06:25 +0100, Liliana Marie Prikler a écrit :
> Am Mittwoch, dem 21.02.2024 um 23:09 +0100 schrieb Vivien Kraus:
> > This would make the old glibmm-2.66 useless.
> Are there really no other users of glibmm-2.64?
I meant for eiciel! Sorry, that was not clear.
Vivien
next prev parent reply other threads:[~2024-02-22 5:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 20:30 [bug#69256] [PATCH gnome-team] gnu: glibmm-2.64: Rename and update to 2.66.6 John Kehayias via Guix-patches via
2024-02-21 22:04 ` [bug#69256] [PATCH gnome-team v2 0/2] Building your glibmm update Vivien Kraus via Guix-patches via
2024-02-18 20:30 ` [bug#69256] [PATCH gnome-team v2 1/2] gnu: glibmm-2.64: Rename and update to 2.66.6 John Kehayias via Guix-patches via
2024-02-21 21:47 ` [bug#69256] [PATCH gnome-team v2 2/2] gnu: eiciel: Update to 0.10.0 Vivien Kraus via Guix-patches via
2024-02-24 6:31 ` bug#69256: [PATCH gnome-team v2 0/2] Building your glibmm update Liliana Marie Prikler
2024-02-21 22:09 ` [bug#69256] [PATCH gnome-team] gnu: glibmm-2.64: Rename and update to 2.66.6 Vivien Kraus via Guix-patches via
2024-02-22 5:25 ` Liliana Marie Prikler
2024-02-22 5:43 ` Vivien Kraus via Guix-patches via [this message]
2024-02-22 5:51 ` Vivien Kraus via Guix-patches via
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=cc649234b373816328b6b9f2abde60ff20f4c857.camel@planete-kraus.eu \
--to=guix-patches@gnu.org \
--cc=69256@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=liliana.prikler@gmail.com \
--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.