Github messages for voidlinux
 help / color / mirror / Atom feed
From: fanyx <fanyx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: hydrus-502
Date: Sat, 15 Oct 2022 01:43:29 +0200	[thread overview]
Message-ID: <20221014234329.uDzGLUpxo5ftZrifHHeNvrewdPKEsCcMkLQjUzpK4_M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35034@inbox.vuxu.org>

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

New review comment by fanyx on void-packages repository

https://github.com/void-linux/void-packages/pull/35034#discussion_r996217060

Comment:
Yeah, i'll submit it and see if they accept.

  parent reply	other threads:[~2022-10-14 23:43 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 18:27 [PR PATCH] New package: hydrus-468 fanyx
2022-01-13 19:49 ` [PR PATCH] [Updated] " fanyx
2022-02-20 13:33 ` [PR PATCH] [Updated] New package: hydrus-469 fanyx
2022-06-08  9:50 ` [PR PATCH] [Updated] New package: hydrus-474 fanyx
2022-06-08  9:51 ` fanyx
2022-06-10 15:21 ` fanyx
2022-06-10 15:37 ` fanyx
2022-06-10 15:40 ` [PR PATCH] [Updated] New package: hydrus-488d fanyx
2022-09-09  2:15 ` github-actions
2022-09-09  9:48 ` [PR PATCH] [Updated] " fanyx
2022-09-20 13:51 ` New package: hydrus-499 fanyx
2022-09-20 13:54 ` [PR PATCH] [Updated] " fanyx
2022-09-20 14:11 ` fanyx
2022-09-20 14:16 ` fanyx
2022-09-20 14:36 ` fanyx
2022-10-05 19:20 ` RunningDroid
2022-10-05 19:23 ` [PR REVIEW] " RunningDroid
2022-10-11 10:36 ` [PR PATCH] [Updated] " fanyx
2022-10-11 10:36 ` [PR REVIEW] " fanyx
2022-10-11 10:36 ` fanyx
2022-10-11 10:37 ` [PR PATCH] [Updated] " fanyx
2022-10-11 10:38 ` fanyx
2022-10-11 10:39 ` fanyx
2022-10-14 10:18 ` [PR PATCH] [Updated] New package: hydrus-501 fanyx
2022-10-14 21:40 ` [PR REVIEW] New package: hydrus-502 paper42
2022-10-14 21:40 ` paper42
2022-10-14 21:40 ` paper42
2022-10-14 21:40 ` paper42
2022-10-14 21:40 ` paper42
2022-10-14 21:40 ` paper42
2022-10-14 21:40 ` paper42
2022-10-14 21:40 ` paper42
2022-10-14 23:43 ` fanyx [this message]
2022-10-14 23:44 ` fanyx
2022-10-14 23:46 ` fanyx
2022-10-14 23:46 ` fanyx
2022-10-15 10:30 ` [PR PATCH] [Updated] " fanyx
2022-10-15 10:31 ` [PR REVIEW] " fanyx
2022-10-15 10:32 ` fanyx
2022-10-15 10:33 ` fanyx
2022-10-15 10:40 ` [PR PATCH] [Updated] " fanyx
2022-10-15 10:42 ` [PR REVIEW] " fanyx
2022-10-15 10:42 ` fanyx
2022-10-15 10:44 ` [PR PATCH] [Updated] " fanyx
2022-10-16 12:24 ` fanyx
2022-10-17  7:00 ` fanyx
2022-10-17  7:02 ` fanyx
2022-10-25 13:01 ` fanyx
2022-10-27 13:27 ` [PR PATCH] [Updated] New package: hydrus-503 fanyx
2022-11-17  9:28 ` [PR PATCH] [Updated] New package: hydrus-504 fanyx
2022-11-17 10:32 ` [PR REVIEW] New package: hydrus-506 fanyx
2023-01-23 22:56 ` [PR PATCH] [Updated] " fanyx
2023-01-23 22:59 ` [PR PATCH] [Updated] New package: hydrus-513 fanyx
2023-01-30 11:19 ` fanyx
2023-01-30 11:19 ` fanyx
2023-02-09  9:16 ` fanyx
2023-04-26 12:58 ` fanyx
2023-04-28  8:01 ` [PR PATCH] [Updated] New package: hydrus-524 fanyx
2023-06-28 20:07 ` [PR PATCH] [Merged]: New package: hydrus-525a Duncaen

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=20221014234329.uDzGLUpxo5ftZrifHHeNvrewdPKEsCcMkLQjUzpK4_M@z \
    --to=fanyx@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).