Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: chatterino2: update to 2.3.4.
Date: Sat, 02 Apr 2022 23:39:47 +0200	[thread overview]
Message-ID: <20220402213947.CSifjZO73l6an5n6t6yYZ_qywo6ZmYme8Rau8MQGvAY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32199@inbox.vuxu.org>

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

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

chatterino2: update to 2.3.4.
https://github.com/void-linux/void-packages/pull/32199

Description:
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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-04-02 21:39 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-25 20:31 [PR PATCH] chatterino2: update to 2.3.3 33kk
2021-07-26  3:01 ` ericonr
2021-07-26 17:22 ` 33kk
2021-07-26 19:33 ` [PR REVIEW] " ericonr
2021-07-26 20:40 ` [PR PATCH] [Updated] " 33kk
2021-07-26 20:42 ` 33kk
2021-07-26 20:57 ` [PR PATCH] [Updated] " 33kk
2021-07-31  2:20 ` [PR REVIEW] " ericonr
2021-07-31  2:20 ` ericonr
2021-07-31 15:04 ` [PR REVIEW] " 33kk
2021-08-01  0:57 ` ericonr
2021-08-01  2:43 ` [PR PATCH] [Updated] " 33kk
2021-08-01  3:38 ` 33kk
2021-08-03  3:43 ` [PR REVIEW] " ericonr
2021-08-03  3:43 ` ericonr
2021-08-03  3:43 ` ericonr
2021-08-03  8:19 ` [PR PATCH] [Updated] " 33kk
2021-08-03  8:21 ` 33kk
2021-08-03  8:25 ` 33kk
2021-08-03 12:07 ` Francesco149
2021-08-03 14:13 ` [PR REVIEW] " ericonr
2021-08-03 15:03 ` 33kk
2021-08-03 15:10 ` 33kk
2021-08-03 17:27 ` ericonr
2021-08-03 21:10 ` 33kk
2021-08-05 18:34 ` [PR PATCH] [Updated] " 33kk
2021-08-05 18:36 ` [PR PATCH] [Updated] chatterino2: update to 2.3.4 33kk
2021-08-05 20:18 ` [PR REVIEW] " zneix
2021-08-06 19:01 ` ericonr
2021-08-06 19:02 ` ericonr
2021-08-06 19:45 ` [PR PATCH] [Updated] " 33kk
2022-03-01 21:26 ` tibequadorian
2022-03-01 21:30 ` tibequadorian
2022-04-02 21:39 ` paper42
2022-04-02 21:39 ` paper42 [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=20220402213947.CSifjZO73l6an5n6t6yYZ_qywo6ZmYme8Rau8MQGvAY@z \
    --to=paper42@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).