From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: yabridgectl-4.0.2
Date: Mon, 26 Sep 2022 10:39:37 +0200 [thread overview]
Message-ID: <20220926083937.RJKjQInu2lohDsCcpNDtBPyZVEEiZK_pNkiXf-EKxFc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39476@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/39476#issuecomment-1257693151
Comment:
please force push to update an existing PR instead of spamming everyone with closing and opening a new one https://github.com/void-linux/void-packages/pull/39474
> xlint check complains about the wrksrc not being top level. The source of yabridgectl is distributed within the yabridge source and is several levels down. Compiles and works well by keeping the origin source in the correct locations and having the multilevel wrksrc set.
try using build_wrksrc
next prev parent reply other threads:[~2022-09-26 8:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 8:17 [PR PATCH] " ajtcode71
2022-09-26 8:39 ` paper42 [this message]
2022-09-26 8:40 ` [PR REVIEW] " paper42
2022-09-26 10:22 ` [PR PATCH] [Updated] " ajtcode71
2022-09-26 11:08 ` [PR REVIEW] " paper42
2022-09-26 11:10 ` paper42
2022-09-26 23:38 ` [PR PATCH] [Updated] " ajtcode71
2022-09-26 23:45 ` ajtcode71
2022-09-27 0:35 ` [PR REVIEW] " paper42
2022-10-01 8:10 ` [PR PATCH] [Updated] " ajtcode71
2022-10-01 8:16 ` ajtcode71
2022-10-01 8:19 ` ajtcode71
2022-10-01 8:25 ` ajtcode71
2022-10-01 10:57 ` [PR REVIEW] " paper42
2022-12-31 1:55 ` github-actions
2023-01-15 2:00 ` [PR PATCH] [Closed]: " github-actions
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=20220926083937.RJKjQInu2lohDsCcpNDtBPyZVEEiZK_pNkiXf-EKxFc@z \
--to=paper42@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).