From: boomlinde <boomlinde@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Update libsidplayfp (to 2.3.1) and libsidplay (to 2.2.3)
Date: Sat, 29 Oct 2022 03:10:58 +0200 [thread overview]
Message-ID: <20221029011058.W640TVxkU90FU7Hq8EOrY6So1XRX7FsaktyB-3p1oSk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40214@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 216 bytes --]
New comment by boomlinde on void-packages repository
https://github.com/void-linux/void-packages/pull/40214#issuecomment-1295673008
Comment:
> please add the email you used to commit to your github account
Done
next prev parent reply other threads:[~2022-10-29 1:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 0:41 [PR PATCH] Update libsidplayfp and libsidplay boomlinde
2022-10-29 0:52 ` classabbyamp
2022-10-29 1:10 ` boomlinde [this message]
2022-10-30 19:38 ` [PR PATCH] [Merged]: Update libsidplayfp (to 2.3.1) and libsidplay (to 2.2.3) classabbyamp
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221029011058.W640TVxkU90FU7Hq8EOrY6So1XRX7FsaktyB-3p1oSk@z \
--to=boomlinde@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).