From: Aurora via Guix-patches via <guix-patches@gnu.org>
To: 54507@debbugs.gnu.org
Cc: Aurora <rind38@disroot.org>
Subject: [bug#54507] [PATCH v3 3/3] gnu: openfst-1.7.3: Enable ngram-fst extension & C++14 build
Date: Thu, 24 Mar 2022 16:01:53 -0400 [thread overview]
Message-ID: <874k3ni0ge.fsf@disp3269> (raw)
In-Reply-To: <20220324195933.2129-4-rind38@disroot.org>
I just finished building this again, just to make sure.
I also added that cover letter to summarize just what the changes and
rationales behind them were.
next prev parent reply other threads:[~2022-03-24 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 17:39 [bug#54507] [PATCH 1/2] gnu: openfst: Add 1.7.3 for kaldi Aurora via Guix-patches via
2022-03-21 17:42 ` [bug#54507] [PATCH 2/2] gnu: kaldi: Update to 498b25d, add vector fix patch, bypass tests Aurora via Guix-patches via
2022-03-21 17:50 ` [bug#54507] gnu: kaldi: " Aurora via Guix-patches via
2022-03-22 20:51 ` [bug#54507] [PATCH v2 1/2] gnu: openfst: Add 1.7.3 for kaldi Aurora via Guix-patches via
2022-03-22 20:51 ` [bug#54507] [PATCH v2 2/2] gnu: kaldi: Update to dd107fd, bypass tests Aurora via Guix-patches via
2022-03-24 11:41 ` [bug#54507] [PATCH 1/2] gnu: openfst: Add 1.7.3 for kaldi Ludovic Courtès
2022-03-24 18:05 ` Aurora via Guix-patches via
2022-03-24 19:59 ` [bug#54507] [PATCH v3 0/3] Add openfst 1.7.3 with extensions " Aurora via Guix-patches via
2022-03-24 19:59 ` [bug#54507] [PATCH v3 1/3] gnu: openfst: Add 1.7.3 " Aurora via Guix-patches via
2022-03-24 19:59 ` [bug#54507] [PATCH v3 2/3] gnu: kaldi: Update to dd107fd, bypass tests Aurora via Guix-patches via
2022-03-24 19:59 ` [bug#54507] [PATCH v3 3/3] gnu: openfst-1.7.3: Enable ngram-fst extension & C++14 build Aurora via Guix-patches via
2022-03-24 20:01 ` Aurora via Guix-patches via [this message]
2022-04-03 23:12 ` Aurora via Guix-patches via
2022-04-04 0:56 ` Aurora via Guix-patches via
2022-05-15 20:30 ` bug#54507: [PATCH 1/2] gnu: openfst: Add 1.7.3 for kaldi Ludovic Courtès
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=874k3ni0ge.fsf@disp3269 \
--to=guix-patches@gnu.org \
--cc=54507@debbugs.gnu.org \
--cc=rind38@disroot.org \
/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).