From: Nathan-MV <Nathan-MV@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Komikku: update to 0.39.0.
Date: Sun, 24 Jul 2022 18:44:48 +0200 [thread overview]
Message-ID: <20220724164448.k3uMnvKNH_h1HXTwWYoAqq0jQNz5nwQpVYZLUInzrbk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38248@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
New comment by Nathan-MV on void-packages repository
https://github.com/void-linux/void-packages/pull/38248#issuecomment-1193354355
Comment:
> Once again, please learn how to force push to existing branches to update this PR without closing it and opening a new one. That just spams everyone with useless notifications and the whole review history is lost. If that happens, at least link all of the closed PRs so reviewers check the reviews there.
I have that power now, don't worry, example above.
next prev parent reply other threads:[~2022-07-24 16:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 15:52 [PR PATCH] " Nathan-MV
2022-07-24 15:56 ` paper42
2022-07-24 16:30 ` [PR PATCH] [Updated] " Nathan-MV
2022-07-24 16:44 ` Nathan-MV [this message]
2022-07-25 0:07 ` Nathan-MV
2022-07-25 0:08 ` Nathan-MV
2022-07-25 0:20 ` Nathan-MV
2022-07-25 0:37 ` [PR PATCH] [Updated] " Nathan-MV
2022-07-25 0:43 ` Nathan-MV
2022-07-25 0:53 ` [PR PATCH] [Updated] Komikku: update to 0.40.0 Nathan-MV
2022-07-25 1:26 ` Nathan-MV
2022-07-25 2:21 ` Nathan-MV
2022-07-25 18:10 ` abenson
2022-07-25 18:10 ` [PR PATCH] [Closed]: " abenson
-- strict thread matches above, loose matches on Subject: below --
2022-07-24 6:05 [PR PATCH] Komikku: update to 0.39.0 Nathan-MV
2022-07-24 6:10 ` classabbyamp
2022-07-24 6:23 ` Nathan-MV
2022-07-24 6:26 ` Nathan-MV
2022-07-24 6:27 ` Nathan-MV
2022-07-24 6:29 ` classabbyamp
2022-07-24 13:37 ` hervyqa
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=20220724164448.k3uMnvKNH_h1HXTwWYoAqq0jQNz5nwQpVYZLUInzrbk@z \
--to=nathan-mv@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).