From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Replace waf with waf3 where applicable
Date: Sat, 03 Oct 2020 17:25:56 +0200 [thread overview]
Message-ID: <20201003152556.Xd832IDmAGEw-KOJs7UvwW08I675DUgDtveoDKPvvN0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21227@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 335 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/pull/21227#issuecomment-703120491
Comment:
So removing build style isn't practical with current version of ladish. It depends on flowcanvas, inlining build style into few templates would be needed.
However the less of this the better.
next prev parent reply other threads:[~2020-10-03 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 22:30 [PR PATCH] " Chocimier
2020-10-03 15:21 ` [PR PATCH] [Updated] " Chocimier
2020-10-03 15:25 ` Chocimier [this message]
2020-10-03 17:27 ` [PR PATCH] [Merged]: " Chocimier
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=20201003152556.Xd832IDmAGEw-KOJs7UvwW08I675DUgDtveoDKPvvN0@z \
--to=chocimier@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).