From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] fcft: update to 3.1.1
Date: Fri, 20 May 2022 00:31:07 +0200 [thread overview]
Message-ID: <20220519223107.rspiSrN_EZq9vuBpw5XYPIkvhVBf3MKU-vrKqCheDyw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37114@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 224 bytes --]
New review comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/37114#discussion_r877589266
Comment:
Just pushed the new version. I'm testing it right now and it's working well.
next prev parent reply other threads:[~2022-05-19 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 1:05 [PR PATCH] " cinerea0
2022-05-19 17:17 ` [PR REVIEW] " ericonr
2022-05-19 22:28 ` [PR PATCH] [Updated] " cinerea0
2022-05-19 22:31 ` cinerea0 [this message]
2022-05-21 8:29 ` fcft: update to 3.1.2 paper42
2022-05-21 8:29 ` [PR PATCH] [Closed]: " paper42
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=20220519223107.rspiSrN_EZq9vuBpw5XYPIkvhVBf3MKU-vrKqCheDyw@z \
--to=cinerea0@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).