From: akierig <akierig@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Signal-Desktop: update to 5.33
Date: Mon, 28 Feb 2022 04:40:04 +0100 [thread overview]
Message-ID: <20220228034004.0CFU2FW-fijmQdH6LCcy4sBqoqt1F13Aj17jNMdfzUs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35882@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
New comment by akierig on void-packages repository
https://github.com/void-linux/void-packages/pull/35882#issuecomment-1053850803
Comment:
> From CONTRIBUTING.md:
>
> > When you make changes to your pull request, please _do not close and reopen your pull request_. Instead, just [forcibly git push](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#review), overwriting any old commits. Closing and opening your pull requests repeatedly spams the Void maintainers.
that's on me, sorry. I hate using GH and `git` generally, I find them incredibly frustrating. So when I get tripped up by a typo in my formatting, it was my default reaction. sorry again.
next prev parent reply other threads:[~2022-02-28 3:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 0:59 [PR PATCH] " akierig
2022-02-28 1:17 ` tibequadorian
2022-02-28 1:17 ` tibequadorian
2022-02-28 3:40 ` akierig [this message]
2022-03-03 13:48 ` tibequadorian
2022-03-04 6:00 ` akierig
2022-03-04 6:15 ` tibequadorian
2022-03-05 0:15 ` [PR PATCH] [Closed]: " akierig
2022-03-05 0:59 ` akierig
2022-03-05 0:59 ` akierig
2022-03-05 4:50 ` [PR PATCH] [Updated] " akierig
2022-03-05 4:57 ` [PR PATCH] [Updated] Signal-Desktop: update to 5.34 akierig
2022-03-05 10:36 ` paper42
2022-03-05 20:15 ` [PR PATCH] [Updated] " akierig
2022-03-05 20:49 ` akierig
2022-03-05 20:50 ` akierig
2022-03-05 21:18 ` akierig
2022-03-06 13:36 ` [PR PATCH] [Merged]: " paper42
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=20220228034004.0CFU2FW-fijmQdH6LCcy4sBqoqt1F13Aj17jNMdfzUs@z \
--to=akierig@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).