From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: go: add build_style=go to avoid code duplication
Date: Mon, 30 Mar 2020 05:36:04 +0200 [thread overview]
Message-ID: <20200330033604.q4ef_BMftvjGkOuk8ZOrOem2yHmKUH50wkMIUg_0i04@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20435@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 436 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/20435#issuecomment-605764728
Comment:
ec937e4d293c642dc45c20deef479dc79d80751a and 927e7904637a29650019668ee193d13efb2afda0 addressed the functional concerns of this, other than that it doesn't really make sense to set `build-style` here as there is too much of a mismatch and attempting to merge them would create more code than remove.
next prev parent reply other threads:[~2020-03-30 3:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20435@inbox.vuxu.org>
2020-03-29 5:58 ` ericonr
2020-03-29 22:23 ` Johnnynator
2020-03-30 2:14 ` ericonr
2020-03-30 3:13 ` q66
2020-03-30 3:14 ` q66
2020-03-30 3:36 ` q66 [this message]
2020-03-30 3:36 ` [PR PATCH] [Closed]: " q66
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=20200330033604.q4ef_BMftvjGkOuk8ZOrOem2yHmKUH50wkMIUg_0i04@z \
--to=q66@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).