Github messages for voidlinux
 help / color / mirror / Atom feed
From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: python3-matrix-nio: adopt, update to 0.20.1, update deps
Date: Fri, 02 Dec 2022 01:18:05 +0100	[thread overview]
Message-ID: <20221202001805.arxONuICE5dLVCEH-yoLMc85CMQ_6qXevw0K6p-j114@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40596@inbox.vuxu.org>

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

There's a closed pull request on the void-packages repository

python3-matrix-nio: adopt, update to 0.20.1, update deps
https://github.com/void-linux/void-packages/pull/40596

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

Talked about this with @non-Jedi, he's okay with me adopting his packages.

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


      parent reply	other threads:[~2022-12-02  0:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 13:49 [PR PATCH] " jcgruenhage
2022-11-18 14:28 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-18 16:56 ` jcgruenhage
2022-11-18 19:09 ` icp1994
2022-11-18 19:49 ` [PR REVIEW] " icp1994
2022-11-18 19:49 ` icp1994
2022-11-18 19:49 ` icp1994
2022-11-18 19:49 ` icp1994
2022-11-18 19:49 ` icp1994
2022-11-18 19:49 ` icp1994
2022-11-18 19:49 ` icp1994
2022-11-18 19:49 ` icp1994
2022-11-19 11:06 ` jcgruenhage
2022-11-19 11:16 ` jcgruenhage
2022-11-19 11:18 ` jcgruenhage
2022-11-19 11:19 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-19 11:23 ` jcgruenhage
2022-11-19 12:35 ` [PR REVIEW] " icp1994
2022-11-19 13:00 ` icp1994
2022-11-19 13:25 ` jcgruenhage
2022-11-27 12:27 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-27 12:28 ` [PR REVIEW] " jcgruenhage
2022-11-27 12:29 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-27 12:54 ` jcgruenhage
2022-11-28 16:57 ` non-Jedi
2022-11-30 10:08 ` [PR PATCH] [Updated] " jcgruenhage
2022-12-02  0:18 ` Piraty [this message]

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=20221202001805.arxONuICE5dLVCEH-yoLMc85CMQ_6qXevw0K6p-j114@z \
    --to=piraty@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).