From: daniel-eys <daniel-eys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] tor: update to 0.4.6.7.
Date: Wed, 25 Aug 2021 01:27:55 +0200 [thread overview]
Message-ID: <20210824232755.MfmSbto6loo4tsMVNJZojyPP5i-2cFl-jwoI3jG80zI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32607@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 221 bytes --]
New review comment by daniel-eys on void-packages repository
https://github.com/void-linux/void-packages/pull/32607#discussion_r695282996
Comment:
ok done (even though the gitweb url is actually still working for me)
next prev parent reply other threads:[~2021-08-24 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 22:08 [PR PATCH] " daniel-eys
2021-08-23 19:52 ` [PR REVIEW] " paper42
2021-08-24 23:16 ` [PR PATCH] [Closed]: " daniel-eys
2021-08-24 23:23 ` [PR PATCH] [Updated] " daniel-eys
2021-08-24 23:27 ` daniel-eys [this message]
2021-08-26 18:31 ` [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=20210824232755.MfmSbto6loo4tsMVNJZojyPP5i-2cFl-jwoI3jG80zI@z \
--to=daniel-eys@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).