From: nielznl <nielznl@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gyazo: update to 1.3.1.
Date: Sun, 08 Nov 2020 00:57:52 +0100 [thread overview]
Message-ID: <20201107235752.IbySGEZvX_g91ak_XzrxMXAYyW5eVvnD4AMymUPFsvs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25639@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
New comment by nielznl on void-packages repository
https://github.com/void-linux/void-packages/pull/25639#issuecomment-723510811
Comment:
> The changes look ok. Maintaining a package usually just means that your opinion might have more weight on some conversation about the package, and you might be mentioned in issues about it. Some people are known to shoot emails at maintainers, as well :)
>
> Feel free to ping maintainers, there are a lot of PRs and it's easy to miss them. And I think you should reopen this one, if you want c:
Thank you for the clarification! I shouldn't have removed my fork tho, now I can not reopen this pull request. I will open a new pull request, I hope it isn't too big of a deal.
next prev parent reply other threads:[~2020-11-07 23:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 18:37 [PR PATCH] " nielznl
2020-10-15 18:48 ` [PR PATCH] [Updated] " nielznl
2020-10-20 18:34 ` [PR REVIEW] " ahesford
2020-10-20 18:42 ` ericonr
2020-10-20 19:28 ` [PR PATCH] [Updated] " nielznl
2020-10-20 19:35 ` [PR REVIEW] " DirectorX
2020-10-20 19:38 ` DirectorX
2020-10-20 19:46 ` [PR PATCH] [Updated] " nielznl
2020-10-20 20:16 ` [PR REVIEW] " nielznl
2020-11-07 22:33 ` [PR PATCH] [Closed]: " nielznl
2020-11-07 22:36 ` ericonr
2020-11-07 22:50 ` nielznl
2020-11-07 22:58 ` ericonr
2020-11-07 22:58 ` ericonr
2020-11-07 23:57 ` nielznl [this message]
2020-11-08 1:47 ` ericonr
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=20201107235752.IbySGEZvX_g91ak_XzrxMXAYyW5eVvnD4AMymUPFsvs@z \
--to=nielznl@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).