all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Anadon <joshua.r.marshall.1991@gmail.com>
Cc: 54630@debbugs.gnu.org
Subject: [bug#54630] [PATCH] utfcpp v3.2.1
Date: Sun, 10 Apr 2022 14:18:02 -0400	[thread overview]
Message-ID: <YlMfWhHBx0FM7QaA@jasmine.lan> (raw)
In-Reply-To: <CAFkJGRf_wg9UOz9z0iCJ7G96NY78YdJ6qpmCKdgXhVJr4Gxx6g@mail.gmail.com>

On Fri, Apr 08, 2022 at 08:33:29PM -0400, Anadon wrote:
> Bump

We are waiting for you to tell us, after applying this update, do all
the dependent packages still work?

You could also answer Tobias's question about naming, although remember
that you are free to use any name you choose.




  reply	other threads:[~2022-04-10 18:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 21:48 [bug#54630] [PATCH] utfcpp v3.2.1 Anadon
2022-03-29 22:10 ` Leo Famulari
2022-03-31  3:43   ` Anadon
2022-04-02  3:56     ` Anadon
2022-04-09  0:33       ` Anadon
2022-04-10 18:18         ` Leo Famulari [this message]
2022-04-10 18:56           ` Anadon
2022-04-10 20:41             ` Tobias Geerinckx-Rice via Guix-patches via
2022-05-22  4:23               ` Maxim Cournoyer
2022-05-22 14:46                 ` Anadon
2022-05-22 15:09                   ` Tobias Geerinckx-Rice via Guix-patches via
2022-05-22 17:41                     ` Anadon
2022-05-29 17:50                       ` Anadon
2022-05-29 18:20                         ` Liliana Marie Prikler
2022-06-04 17:37                           ` Anadon
2022-06-06 14:06                             ` bug#54630: " Maxim Cournoyer
2022-04-02 22:44 ` [bug#54630] " Tobias Geerinckx-Rice via Guix-patches via
2022-05-27  3:03 ` [bug#54630] [PATCH] Updating to add utfcpp as a seperate version and to update mkvtoolnix and warzone2100 to use the old version since they need behavior from version 2 and not version 3 Anadon
2022-05-27  6:51   ` Liliana Marie Prikler
2022-05-27  3:37 ` Anadon

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=YlMfWhHBx0FM7QaA@jasmine.lan \
    --to=leo@famulari.name \
    --cc=54630@debbugs.gnu.org \
    --cc=joshua.r.marshall.1991@gmail.com \
    /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.