From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: 54630@debbugs.gnu.org
Subject: [bug#54630] [PATCH] utfcpp v3.2.1
Date: Sun, 03 Apr 2022 00:44:41 +0200 [thread overview]
Message-ID: <3a7bb6655fcc60440e7030c5f3d5eedb@tobias.gr> (raw)
In-Reply-To: <CAFkJGRddNbOPc0UOtT6zJDVevHn4WZLwd6FLbDFRJASKmC5tYg@mail.gmail.com>
Anadon,
As begun in #guix: I've applied the patch (with a few modifications) and
will build all dependents overnight.
I've changed utfcpp-2 to inherit from utfcpp and removed the indirection
(via the unused utfcpp-3) of the latter.
Whilst Guix tolerates to the point of accepting pseudonyms in copyright
statements, yours seems rather… redundant? Is there a compelling reason
not to use the name in your e-mail address? Is it also a pseudonym?
Kind regards,
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2022-04-02 22:45 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
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 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
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=3a7bb6655fcc60440e7030c5f3d5eedb@tobias.gr \
--to=guix-patches@gnu.org \
--cc=54630@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.