From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] python3 lsp server 1.6.0
Date: Wed, 09 Nov 2022 17:25:53 +0100 [thread overview]
Message-ID: <20221109162553.J_GcKLdg_aXoShipxQOxzy_xcXoSSA1S32EZvnDawdQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40393@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 227 bytes --]
New review comment by icp1994 on void-packages repository
https://github.com/void-linux/void-packages/pull/40393#discussion_r1018157301
Comment:
```suggestion
hostmakedepends="python3-setuptools_scm"
depends="python3"
```
next prev parent reply other threads:[~2022-11-09 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 20:03 [PR PATCH] " CameronNemo
2022-11-09 16:25 ` icp1994 [this message]
2022-11-10 10:14 ` [PR REVIEW] " paper42
2022-11-10 10:14 ` paper42
2022-11-10 18:59 ` [PR PATCH] [Updated] " CameronNemo
2022-11-10 19:03 ` CameronNemo
2022-11-10 19:23 ` [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=20221109162553.J_GcKLdg_aXoShipxQOxzy_xcXoSSA1S32EZvnDawdQ@z \
--to=icp1994@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).