Github messages for voidlinux
 help / color / mirror / Atom feed
From: fosslinux <fosslinux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python-pyQt5 fixes
Date: Wed, 27 May 2020 22:50:32 +0200	[thread overview]
Message-ID: <20200527205032.3JCrzn5C2HyNbGDyfy2KNMgUwTDHiIlEhzmobuUBqug@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22109@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 310 bytes --]

New comment by fosslinux on void-packages repository

https://github.com/void-linux/void-packages/pull/22109#issuecomment-634931969

Comment:
Oh, that is quite unfortunate. No pressure, but you could use sources.voidlinux.org, if all that you need to do is get the source code? No problem if you can't though.

  parent reply	other threads:[~2020-05-27 20:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19  3:21 [PR PATCH] " fosslinux
2020-05-19  9:56 ` fosslinux
2020-05-19  9:57 ` fosslinux
2020-05-21 11:49 ` sgn
2020-05-21 22:37 ` [PR PATCH] [Updated] " fosslinux
2020-05-21 22:39 ` fosslinux
2020-05-21 23:11 ` sgn
2020-05-22  0:30 ` [PR PATCH] [Updated] " fosslinux
2020-05-22  0:30 ` fosslinux
2020-05-25  1:09 ` fosslinux
2020-05-27 14:37 ` sgn
2020-05-27 20:50 ` fosslinux [this message]
2020-07-21  7:25 ` [PR PATCH] [Updated] " fosslinux
2020-07-21  7:25 ` fosslinux
2020-07-30  9:28 ` fosslinux
2020-08-03  9:20 ` Piraty
2020-08-03 10:05 ` Piraty
2020-08-03 10:26 ` fosslinux
2020-08-05  8:16 ` [PR PATCH] [Updated] " fosslinux
2020-08-05  8:17 ` fosslinux
2020-08-11  0:06 ` [PR REVIEW] " Piraty
2020-08-11  0:31 ` fosslinux
2020-08-11  0:34 ` ericonr
2020-08-11  0:41 ` sgn
2020-08-11  6:09 ` fosslinux
2020-08-11  6:10 ` fosslinux
2020-08-11  6:10 ` fosslinux
2020-08-11  6:10 ` [PR PATCH] [Closed]: " fosslinux

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=20200527205032.3JCrzn5C2HyNbGDyfy2KNMgUwTDHiIlEhzmobuUBqug@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).