From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] tox: update to 3.28.0, orphan.
Date: Sat, 18 Feb 2023 20:09:03 +0100 [thread overview]
Message-ID: <20230218190903.mTiidejxKdS4_E2pIBiPgRQA4h27x1HuNvieP8a70WY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42299@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 201 bytes --]
New review comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/pull/42299#discussion_r1111094563
Comment:
OK, even if ignoring 4.* wasn't intended to commit.
next prev parent reply other threads:[~2023-02-18 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 20:51 [PR PATCH] " Chocimier
2023-02-16 1:11 ` [PR REVIEW] " classabbyamp
2023-02-16 1:11 ` classabbyamp
2023-02-16 1:11 ` classabbyamp
2023-02-18 19:08 ` [PR PATCH] [Updated] " Chocimier
2023-02-18 19:09 ` Chocimier [this message]
2023-02-20 21:57 ` [PR PATCH] [Merged]: " Chocimier
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=20230218190903.mTiidejxKdS4_E2pIBiPgRQA4h27x1HuNvieP8a70WY@z \
--to=chocimier@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).