From: ifreund <ifreund@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] update river and waylock
Date: Sat, 01 Apr 2023 01:45:29 +0200 [thread overview]
Message-ID: <20230331234529.EMpofVlS5WpB-8Kdpdga4-4ukP5D4c-q3TWwqTrUzSY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43143@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 187 bytes --]
New review comment by ifreund on void-packages repository
https://github.com/void-linux/void-packages/pull/43143#discussion_r1155001929
Comment:
Should scdoc not be in hostmakedepends?
next prev parent reply other threads:[~2023-03-31 23:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 15:08 [PR PATCH] " dkwo
2023-03-31 15:17 ` icp1994
2023-03-31 15:22 ` [PR PATCH] [Updated] " dkwo
2023-03-31 15:30 ` icp1994
2023-03-31 18:37 ` [PR PATCH] [Updated] " dkwo
2023-03-31 18:38 ` dkwo
2023-03-31 23:45 ` [PR REVIEW] " ifreund
2023-03-31 23:45 ` ifreund
2023-03-31 23:45 ` ifreund [this message]
2023-03-31 23:45 ` ifreund
2023-03-31 23:45 ` ifreund
2023-04-01 11:01 ` classabbyamp
2023-04-01 12:27 ` ifreund
2023-04-01 14:09 ` [PR PATCH] [Updated] " dkwo
2023-04-01 14:10 ` [PR REVIEW] " dkwo
2023-04-01 14:10 ` dkwo
2023-04-01 14:10 ` dkwo
2023-04-01 14:11 ` dkwo
2023-04-01 14:13 ` dkwo
2023-04-01 14:14 ` dkwo
2023-04-01 14:15 ` [PR PATCH] [Updated] " dkwo
2023-04-01 14:16 ` [PR REVIEW] " dkwo
2023-04-01 16:49 ` paper42
2023-04-01 17:08 ` classabbyamp
2023-04-01 17:29 ` icp1994
2023-04-01 17:32 ` classabbyamp
2023-04-02 0:04 ` [PR REVIEW] " dkwo
2023-04-02 0:07 ` [PR PATCH] [Updated] " dkwo
2023-04-02 12:36 ` [PR REVIEW] " dkwo
2023-04-02 12:41 ` dkwo
2023-04-02 13:12 ` paper42
2023-04-03 0:42 ` [PR PATCH] [Updated] " dkwo
2023-04-03 0:52 ` dkwo
2023-04-03 0:58 ` dkwo
2023-04-03 7:45 ` paper42
2023-04-06 16:35 ` [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=20230331234529.EMpofVlS5WpB-8Kdpdga4-4ukP5D4c-q3TWwqTrUzSY@z \
--to=ifreund@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).