From: Vagrant Cascadian <vagrant@debian.org>
To: 72881@debbugs.gnu.org
Cc: vagrant@debian.org
Subject: [bug#72881] lcrq and lcsync updates
Date: Thu, 29 Aug 2024 14:35:38 -0700 [thread overview]
Message-ID: <87jzfzui51.fsf@wireframe> (raw)
[-- Attachment #1: Type: text/plain, Size: 214 bytes --]
The forthcoming patches update lcrq to 0.2.1 and lcsync to 0.3.1, and
pass some additional compiler optimizations to the lcrq build.
lcrq, librecast and lcsync all build fine afte rthe fact.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2024-08-29 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 21:35 Vagrant Cascadian [this message]
2024-08-29 21:39 ` [bug#72881] [PATCH 1/3] gnu: lcrq: Update to 0.2.1 vagrant
2024-08-29 21:39 ` [bug#72881] [PATCH 2/3] gnu: lcsync: Update to 0.3.1 vagrant
2024-08-29 21:39 ` [bug#72881] [PATCH 3/3] gnu: lcrq: Add compiler optimizations vagrant
2024-09-06 21:12 ` bug#72881: lcrq and lcsync updates Vagrant Cascadian
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=87jzfzui51.fsf@wireframe \
--to=vagrant@debian.org \
--cc=72881@debbugs.gnu.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).