From: sug0 <sug0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: common/environment/build-style/go.sh: allow setting CGO_ENABLED
Date: Sat, 14 Jan 2023 14:07:34 +0100 [thread overview]
Message-ID: <20230114130734.J6FsXqcjhwlCv5FZq8I4dLF8Rj3Y8Yi-rLMN30BBMQs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41167@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 145 bytes --]
New comment by sug0 on void-packages repository
https://github.com/void-linux/void-packages/pull/41167#issuecomment-1382733786
Comment:
cheers
prev parent reply other threads:[~2023-01-14 13:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 16:31 [PR PATCH] " sug0
2023-01-13 17:24 ` Vaelatern
2023-01-13 18:32 ` sug0
2023-01-13 18:34 ` sug0
2023-01-13 18:49 ` Vaelatern
2023-01-13 19:24 ` classabbyamp
2023-01-13 19:24 ` classabbyamp
2023-01-13 22:35 ` sug0
2023-01-13 23:16 ` Vaelatern
2023-01-13 23:57 ` [PR PATCH] [Merged]: " classabbyamp
2023-01-14 13:07 ` sug0 [this message]
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=20230114130734.J6FsXqcjhwlCv5FZq8I4dLF8Rj3Y8Yi-rLMN30BBMQs@z \
--to=sug0@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).