From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: go: update to 1.12.6
Date: Wed, 12 Jun 2019 20:37:20 +0200 [thread overview]
Message-ID: <20190612183720.OfZPg831mkVbFfKkvqweaZtvjj5K1YwZStACTKA34i4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12424@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
New comment by the-maldridge on void-packages repository
https://github.com/void-linux/void-packages/pull/12424#issuecomment-501402582
Comment:
This should be fine, but I'd like to hold off merging it until the go universe build I'm running now finishes. It would be nice to make sure we aren't going to break things that work.
next prev parent reply other threads:[~2019-06-12 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 10:47 [PR PATCH] " voidlinux-github
2019-06-12 18:37 ` voidlinux-github [this message]
2019-06-12 20:33 ` voidlinux-github
2019-06-14 3:05 ` [PR PATCH] [Closed]: " voidlinux-github
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=20190612183720.OfZPg831mkVbFfKkvqweaZtvjj5K1YwZStACTKA34i4@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).