From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] wcm: update to 0.7.5
Date: Wed, 15 Mar 2023 20:40:19 +0100 [thread overview]
Message-ID: <20230315194019.xvX19GfpCi2GfmubgKtevZ6YnCmq7VlKhaPZQNXszzY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42713@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
New review comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/42713#discussion_r1137684952
Comment:
Enabling that option (as is the default) causes it to build wdisplays as a submodule from an arbitrary git commit in a fork that is not Void's upstream for that project. It's a new option (or at least newer than the previous release) and I can see why the developer included it (no canonical source for wdisplays after the original developer deleted their repo), but it would just cause problems for us.
next prev parent reply other threads:[~2023-03-15 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 2:23 [PR PATCH] " cinerea0
2023-03-15 18:38 ` [PR REVIEW] " abenson
2023-03-15 19:40 ` cinerea0 [this message]
2023-03-15 19:54 ` [PR PATCH] [Merged]: " abenson
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=20230315194019.xvX19GfpCi2GfmubgKtevZ6YnCmq7VlKhaPZQNXszzY@z \
--to=cinerea0@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).