From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org, Anisse Astier <anisse@astier.eu>,
Christian Stewart <christian@aperture.us>
Subject: Re: [Buildroot] [PATCH v6 1/1] package/tailscale: new package
Date: Mon, 28 Oct 2024 22:30:27 +0100 [thread overview]
Message-ID: <20241028223027.0bfbd782@windsurf> (raw)
In-Reply-To: <20241028162926.209397-1-james.hilliard1@gmail.com>
On Mon, 28 Oct 2024 10:29:26 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> Changes v5 -> v6:
> - bump to version 1.76.1
> Changes v4 -> v5:
> - bump to version 1.72.0
> - remove GOPROXY override
> Changes v3 -> v4:
> - restore GOPROXY override
> Changes v2 -> v3:
> - set required CONFIG_TUN kernel config option
> Changes v1 -> v2:
> - don't set GOPROXY
> ---
> DEVELOPERS | 1 +
> package/Config.in | 1 +
> package/tailscale/Config.in | 8 ++++++++
> package/tailscale/tailscale.hash | 3 +++
> package/tailscale/tailscale.mk | 22 ++++++++++++++++++++++
> 5 files changed, 35 insertions(+)
> create mode 100644 package/tailscale/Config.in
> create mode 100644 package/tailscale/tailscale.hash
> create mode 100644 package/tailscale/tailscale.mk
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-10-28 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 16:29 [Buildroot] [PATCH v6 1/1] package/tailscale: new package James Hilliard
2024-10-28 21:30 ` Thomas Petazzoni via buildroot [this message]
2024-10-28 22:17 ` Christian Stewart via buildroot
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=20241028223027.0bfbd782@windsurf \
--to=buildroot@buildroot.org \
--cc=anisse@astier.eu \
--cc=christian@aperture.us \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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