From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Felix Gruber <felgru@posteo.net>
Cc: 52789-done@debbugs.gnu.org
Subject: bug#52789: [PATCH v2 0/4] Update naev to 0.9.0
Date: Tue, 28 Dec 2021 16:06:40 +0100 [thread overview]
Message-ID: <874k6sahvj.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20211227231946.105095-1-felgru@posteo.net> (Felix Gruber's message of "Mon, 27 Dec 2021 23:19:42 +0000")
Hello,
Felix Gruber <felgru@posteo.net> writes:
> I've updated the patchset to add the ucd-next package as discussed and
> to package version 5.0 of libunibreak.
Thank you. I applied them.
> I'll submit a separate patch for updating ucd to be applied to the
> staging branch.
I tweaked this one because it couldn't be based off changes from master
branch.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2021-12-28 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 13:34 [bug#52789] [PATCH 0/3] Update naev to 0.9.0 Felix Gruber
2021-12-25 13:37 ` [bug#52789] [PATCH 1/3] gnu: Add libunibreak Felix Gruber
2021-12-25 13:37 ` [bug#52789] [PATCH 2/3] gnu: Add naev-artwork Felix Gruber
2021-12-25 13:37 ` [bug#52789] [PATCH 3/3] gnu: naev: Update to 0.9.0 Felix Gruber
2021-12-26 20:54 ` [bug#52789] [PATCH 1/3] gnu: Add libunibreak Nicolas Goaziou
2021-12-27 14:48 ` Felix Gruber
2021-12-27 16:18 ` Nicolas Goaziou
2021-12-27 23:19 ` [bug#52789] [PATCH v2 0/4] Update naev to 0.9.0 Felix Gruber
2021-12-27 23:25 ` [bug#52789] [PATCH staging] gnu: ucd: Update to 14.0.0 Felix Gruber
2021-12-28 15:06 ` Nicolas Goaziou [this message]
2021-12-27 23:19 ` [bug#52789] [PATCH v2 1/4] gnu: Add ucd-next Felix Gruber
2021-12-27 23:19 ` [bug#52789] [PATCH v2 2/4] gnu: Add libunibreak Felix Gruber
2021-12-27 23:19 ` [bug#52789] [PATCH v2 3/4] gnu: Add naev-artwork Felix Gruber
2021-12-27 23:19 ` [bug#52789] [PATCH v2 4/4] gnu: naev: Update to 0.9.0 Felix Gruber
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874k6sahvj.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=52789-done@debbugs.gnu.org \
--cc=felgru@posteo.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).