From: Vagrant Cascadian <vagrant@debian.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 65233@debbugs.gnu.org
Subject: [bug#65233] lcsync and librecast updates
Date: Tue, 29 Aug 2023 11:04:35 -0700 [thread overview]
Message-ID: <87wmxdvi6k.fsf@wireframe> (raw)
In-Reply-To: <87zg29vja5.fsf@wireframe>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On 2023-08-29, Vagrant Cascadian wrote:
> On 2023-08-29, Christopher Baines wrote:
>> Vagrant Cascadian <vagrant@debian.org> writes:
>>
>>> Both lcsync 0.2.1 and librecast 0.7.0 have upstream releases now, thus
>>> removing "WIP" from the title; these are worthy of merging, I hope. :)
>>
>> This looks good to me, I've pushed it to master as
>> 5f672aaa0ca7e2c5775c8950fa1627ac419e557e.
>
> Thanks!
>
> It looks like you ended up merging the old librecast 0.7-RC3 patch,
> rather than the 0.7.0 patch I submitted later. I apparently forgot to
> mark it as a v2 patch, which maybe tripped you up.
>
> Would it be ok if I pushed the newer version or would you be able to?
I just went ahead and pushed c61c499c59109f6094384ee205c98034d759b600 as
a follow-up to update librecast to 0.7.0.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2023-08-29 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 21:06 [bug#65233] WIP lcsync and librecast updates Vagrant Cascadian
2023-08-11 21:11 ` [bug#65233] [PATCH 1/2] gnu: librecast: Update to 0.7-RC3 vagrant
2023-08-11 21:12 ` [bug#65233] [PATCH 2/2] gnu: lcsync: Update to 0.2.1 vagrant
2023-08-22 20:31 ` [bug#65233] [PATCH 1/2] gnu: librecast: Update to 0.7.0 vagrant
2023-08-22 20:31 ` [bug#65233] [PATCH 2/2] gnu: lcsync: Update to 0.2.1 vagrant
2023-08-23 22:02 ` [bug#65233] lcsync and librecast updates Vagrant Cascadian
2023-08-29 12:56 ` bug#65233: " Christopher Baines
2023-08-29 17:40 ` [bug#65233] " Vagrant Cascadian
2023-08-29 18:04 ` Vagrant Cascadian [this message]
2023-08-31 12:30 ` Christopher Baines
2023-08-31 21:52 ` 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=87wmxdvi6k.fsf@wireframe \
--to=vagrant@debian.org \
--cc=65233@debbugs.gnu.org \
--cc=mail@cbaines.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).