Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: David Anderson <dave@natulte.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: (Unofficial) wireguard packages for Debian Stretch (testing)
Date: Sat, 11 Feb 2017 11:04:54 +0100	[thread overview]
Message-ID: <CAHmME9rumLr0V6yD=zoHk-GSN2-bCiGe644WHtt4EJvKrhtLoA@mail.gmail.com> (raw)
In-Reply-To: <CAMx+r7VgJ0xDAy46d28Qv_Vv7vM8JO0yRbYEh6AHVWT55LEVAw@mail.gmail.com>

Hi Dave,

Good idea. I don't like the scary pipe to bash one liners. I'll go
with what you suggested. However, is `linux-headers-amd64` really
required?

Thanks,
Jason

  reply	other threads:[~2017-02-11  9:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-11  0:23 David Anderson
2017-02-11  9:03 ` Jason A. Donenfeld
2017-02-11  9:49   ` David Anderson
2017-02-11 10:04     ` Jason A. Donenfeld [this message]
2017-02-11 10:15       ` David Anderson
2017-02-11 10:17         ` Jason A. Donenfeld
2017-02-11 11:48           ` David Anderson
2017-02-11 13:28             ` Jason A. Donenfeld
2017-02-11 16:27             ` Baptiste Jonglez
2017-02-11 21:38               ` David Anderson
2017-02-11 12:32     ` Jason A. Donenfeld
2017-02-11 21:36       ` David Anderson
2017-02-12  2:40         ` David Anderson
2017-02-12 13:42           ` Jason A. Donenfeld
2017-02-12 23:01 ` Daniel Kahn Gillmor
2017-02-12 23:37   ` Jason A. Donenfeld
2017-02-14  4:55   ` David Anderson
2017-02-14 15:50     ` Daniel Kahn Gillmor
2017-02-15 21:31       ` Baptiste Jonglez
2017-02-17  2:46         ` Daniel Kahn Gillmor
2017-02-17  8:15           ` Baptiste Jonglez
2017-02-17 13:32             ` Jason A. Donenfeld
2017-02-17  3:14       ` David Anderson
2017-02-17 19:49         ` Daniel Kahn Gillmor
2017-02-20 23:53           ` David Anderson
2017-02-21  0:53             ` Ibrahim Tachijian

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='CAHmME9rumLr0V6yD=zoHk-GSN2-bCiGe644WHtt4EJvKrhtLoA@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=dave@natulte.net \
    --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).