From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] pcmanfm-qt: update to 1.2.1
Date: Sat, 07 Jan 2023 19:00:28 +0100 [thread overview]
Message-ID: <20230107180028.BmAYomqR8NtMSUA075bsJ4WPkMcdYsK8yY2zMLXzOH0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41464@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 213 bytes --]
New review comment by abenson on void-packages repository
https://github.com/void-linux/void-packages/pull/41464#discussion_r1064030610
Comment:
If the soname/ABI didn't change, this doesn't need to be updated.
next prev parent reply other threads:[~2023-01-07 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 6:17 [PR PATCH] " zen0bit
2023-01-05 8:39 ` [PR PATCH] [Updated] " zen0bit
2023-01-07 18:00 ` abenson [this message]
2023-01-07 18:40 ` [PR REVIEW] " paper42
2023-01-18 4:46 ` [PR PATCH] [Updated] " zen0bit
2023-01-22 21:01 ` Piraty
2023-01-22 21:01 ` [PR PATCH] [Closed]: " Piraty
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=20230107180028.BmAYomqR8NtMSUA075bsJ4WPkMcdYsK8yY2zMLXzOH0@z \
--to=abenson@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).