From: nilium <nilium@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: NetAuth-ldap-0.1.0
Date: Mon, 24 Aug 2020 07:02:28 +0200 [thread overview]
Message-ID: <20200824050228.l6y2uo9B69rIID1K6hF7n9deLI1ouRP8i5ffM8SsDxU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24451@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 206 bytes --]
New review comment by nilium on void-packages repository
https://github.com/void-linux/void-packages/pull/24451#discussion_r475343879
Comment:
Does this affect anything if it's not used in the exec line?
next prev parent reply other threads:[~2020-08-24 5:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 4:44 [PR PATCH] " the-maldridge
2020-08-24 5:02 ` nilium [this message]
2020-08-24 5:03 ` [PR REVIEW] " the-maldridge
2020-08-24 8:54 ` the-maldridge
2020-08-26 3:34 ` [PR PATCH] [Updated] " the-maldridge
2020-10-02 2:08 ` the-maldridge
2020-10-02 4:50 ` [PR PATCH] [Closed]: " the-maldridge
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=20200824050228.l6y2uo9B69rIID1K6hF7n9deLI1ouRP8i5ffM8SsDxU@z \
--to=nilium@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).