From: "宋文武 via Guix-patches via" <guix-patches@gnu.org>
To: Andy Tai <atai@atai.org>
Cc: 61728@debbugs.gnu.org
Subject: [bug#61728] [PATCH] gnu: flatbuffers: Update to 23.1.21
Date: Thu, 02 Mar 2023 11:24:05 +0800 [thread overview]
Message-ID: <87o7pbq1ii.fsf@envs.net> (raw)
In-Reply-To: <20230223091505.13292-1-atai@atai.org> (Andy Tai's message of "Thu, 23 Feb 2023 01:15:05 -0800")
Andy Tai <atai@atai.org> writes:
> * gnu/packages/serialization.scm (flatbuffers): Update to 23.1.21
Hello, this will broke tensorflow-lite@2.5.0, kodi@19.5 not tested.
next prev parent reply other threads:[~2023-03-02 3:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 9:15 [bug#61728] [PATCH] gnu: flatbuffers: Update to 23.1.21 Andy Tai
2023-03-02 3:24 ` 宋文武 via Guix-patches via [this message]
2023-03-02 6:39 ` Andy Tai
2023-03-02 8:09 ` [bug#61728] [PATCH v2] gnu: Add flatbuffers-next Andy Tai
2023-03-05 21:45 ` bug#61728: [PATCH] gnu: flatbuffers: Update to 23.1.21 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=87o7pbq1ii.fsf@envs.net \
--to=guix-patches@gnu.org \
--cc=61728@debbugs.gnu.org \
--cc=atai@atai.org \
--cc=iyzsong@envs.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).