From: fosslinux <fosslinux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] python-numpy: fix for armv5tel-musl.
Date: Sat, 10 Oct 2020 12:20:44 +0200 [thread overview]
Message-ID: <20201010102044.aj68whJvam4WBxCwYVnRQ1DZbTA8GgqYwgRxRdCkW5k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24988@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
New review comment by fosslinux on void-packages repository
https://github.com/void-linux/void-packages/pull/24988#discussion_r502774431
Comment:
I don't really like that.. the `files/` folder should be independent of any one specific patch/fix that is applied.
next prev parent reply other threads:[~2020-10-10 10:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 8:18 [PR PATCH] " fosslinux
2020-09-20 8:40 ` [PR PATCH] [Updated] " fosslinux
2020-09-20 8:40 ` fosslinux
2020-09-22 6:04 ` [PR PATCH] [Updated] " fosslinux
2020-09-25 0:31 ` [PR REVIEW] " sgn
2020-09-25 8:10 ` fosslinux
2020-09-29 4:39 ` [PR PATCH] [Updated] " fosslinux
2020-10-01 22:52 ` fosslinux
2020-10-09 20:21 ` [PR REVIEW] " ericonr
2020-10-10 2:41 ` fosslinux
2020-10-10 2:59 ` [PR PATCH] [Updated] " fosslinux
2020-10-10 4:21 ` [PR REVIEW] " ericonr
2020-10-10 10:20 ` fosslinux [this message]
2020-12-01 0:27 ` sgn
2020-12-01 0:43 ` sgn
2020-12-01 0:47 ` sgn
2020-12-01 1:10 ` ericonr
2020-12-09 5:08 ` [PR REVIEW] " ahesford
2020-12-09 7:17 ` fosslinux
2020-12-31 1:06 ` [PR PATCH] [Updated] " fosslinux
2020-12-31 1:22 ` fosslinux
2020-12-31 1:22 ` [PR REVIEW] " fosslinux
2020-12-31 1:22 ` fosslinux
2020-12-31 17:59 ` ahesford
2020-12-31 23:34 ` fosslinux
2020-12-31 23:37 ` [PR PATCH] [Updated] " fosslinux
2021-01-06 16:26 ` ahesford
2021-01-06 17:26 ` [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=20201010102044.aj68whJvam4WBxCwYVnRQ1DZbTA8GgqYwgRxRdCkW5k@z \
--to=fosslinux@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).