From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: common/build-style/python3-pep517.sh: unpack wheels for testing
Date: Wed, 12 Apr 2023 21:46:06 +0200 [thread overview]
Message-ID: <20230412194606.7YO9IkdnFqdCG8RuFxH2SpH9dVy0id1t8wbX7Yb_x1w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42013@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 307 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/42013#issuecomment-1505830810
Comment:
> The later commits are for demonstration purpose and not intended for merging.
i think it's fine to merge those changes with this, it's a beneficial cleanup
next prev parent reply other threads:[~2023-04-12 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 14:52 [PR PATCH] " icp1994
2023-04-12 19:46 ` classabbyamp [this message]
2023-04-12 19:55 ` ahesford
2023-04-12 19:55 ` [PR PATCH] [Closed]: " ahesford
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=20230412194606.7YO9IkdnFqdCG8RuFxH2SpH9dVy0id1t8wbX7Yb_x1w@z \
--to=classabbyamp@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).