From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: tailscale: update to 1.38.4.
Date: Sat, 08 Apr 2023 13:04:37 +0200 [thread overview]
Message-ID: <20230408110437.ORarEY0oOBQIBDleOWQ6LFlHvc1W7Vn8hRjz8oG-SrQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43343@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 230 bytes --]
New comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/pull/43343#issuecomment-1500868050
Comment:
I've found a bug in the version string we pass in go_ldflags, trying to find why it happens
next prev parent reply other threads:[~2023-04-08 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 10:57 [PR PATCH] " 0x5c
2023-04-08 11:04 ` 0x5c [this message]
2023-04-08 11:19 ` [PR PATCH] [Updated] " 0x5c
2023-04-08 11:19 ` 0x5c
2023-04-08 15:43 ` [PR PATCH] [Merged]: " paper42
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=20230408110437.ORarEY0oOBQIBDleOWQ6LFlHvc1W7Vn8hRjz8oG-SrQ@z \
--to=0x5c@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).