From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Jannis Pinter <jannis@pinterjann.is>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Compatibiliyt issues between 0.0.20170115 and 0.0.20170517
Date: Thu, 18 May 2017 15:39:48 -0400 [thread overview]
Message-ID: <8737c29cor.fsf@fifthhorseman.net> (raw)
In-Reply-To: <CAHmME9osBYxRKFwSCroHcpORdCj8d8x1=WrE=6iR0DRofB=rAg@mail.gmail.com>
On Thu 2017-05-18 20:43:11 +0200, Jason A. Donenfeld wrote:
> Only use 0.0.20170517.
i think this was the first incompatible revision that has been released.
is that correct?
i know we're in early days with wireguard, and there's no guarantee of
protocol compatibility. but i wonder whether we should signal
explicitly when there is an update that requires both sides to upgrade
at the same time. Should i have put it in the NEWS file in the debian
package, for example? Or are there other forms of signalling that we
should use to communicate this better?
--dkg
next prev parent reply other threads:[~2017-05-18 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 4:35 Compatibiliyt issues between 0.0.20170115 and 0.0.20170517 Jannis Pinter
2017-05-18 18:43 ` Jason A. Donenfeld
2017-05-18 19:39 ` Daniel Kahn Gillmor [this message]
2017-05-18 20:04 ` Bruno Wolff III
2017-05-19 1:26 ` Jannis Pinter
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=8737c29cor.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=Jason@zx2c4.com \
--cc=jannis@pinterjann.is \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.