From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dhcp: No need to specify /dev/random
Date: Sun, 06 Dec 2020 23:56:22 +0100 [thread overview]
Message-ID: <20201206225622.QNecZleLICOAM29cVzuuvljHAW5x4k5izDCRjDeExuY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26961@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/26961#issuecomment-739579295
Comment:
Yea not sure if this change is worth it at all, the back and forth about the commit message etc. (you changed the PR title, not the commit message) it really doesn't matter.
next prev parent reply other threads:[~2020-12-06 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 13:14 [PR PATCH] " firasuke
2020-12-05 19:44 ` [PR REVIEW] " ericonr
2020-12-06 22:18 ` [PR REVIEW] dhcp: " firasuke
2020-12-06 22:56 ` Duncaen
2020-12-06 22:56 ` Duncaen [this message]
2020-12-07 17:59 ` firasuke
2020-12-07 17:59 ` [PR PATCH] [Closed]: " firasuke
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=20201206225622.QNecZleLICOAM29cVzuuvljHAW5x4k5izDCRjDeExuY@z \
--to=duncaen@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).