Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: developer@it-offshore.co.uk
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard added to Alpine Linux
Date: Thu, 2 Mar 2017 07:33:13 -0800	[thread overview]
Message-ID: <CAHmME9ow_=3muSufX_--6JRG0Fz9qfyEPKi_=rc3tJUGr_CaAQ@mail.gmail.com> (raw)
In-Reply-To: <6b590394-3134-b725-a063-0993b32a51c4@it-offshore.co.uk>

Hey Stuart,

Responding with the list CCd, since that's where people learn about
wireguard related things. You might want to subscribe to it so you can
get snapshot bump announcements.

On Wed, Mar 1, 2017 at 10:36 PM, Stuart Cardall
<developer@it-offshore.co.uk> wrote:
> Just a quick courtesy email to let you know wireguard has been added to
> Alpine Linux.

This is wonderful news! Thanks so much for doing this. I left a few
small comments on the PR [1], which should be easy to address. Looking
forward to testing this out.

Could you send a tiny command stanza for wireguard.io/install/ so that
I can put up an Alpine Linux section?

Regards,
Jason

[1] https://github.com/alpinelinux/aports/pull/948#pullrequestreview-24756731

       reply	other threads:[~2017-03-02 15:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6b590394-3134-b725-a063-0993b32a51c4@it-offshore.co.uk>
2017-03-02 15:33 ` Jason A. Donenfeld [this message]
2017-03-02 21:49   ` Stuart Cardall
2017-03-03  3:24     ` Jason A. Donenfeld
2017-03-23 19:39       ` Stuart Cardall
2017-03-08 16:05     ` Release monitoring (Was: Wireguard added to Alpine Linux) Baptiste Jonglez
2017-03-08 17:12       ` Stuart Cardall
2017-03-08 18:05       ` Stuart Cardall
2017-03-10  3:14         ` Jason A. Donenfeld

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='CAHmME9ow_=3muSufX_--6JRG0Fz9qfyEPKi_=rc3tJUGr_CaAQ@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=developer@it-offshore.co.uk \
    --cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).