From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Bruno Wolff III <bruno@wolff.to>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Pre 5.1-rc1 build issue
Date: Wed, 13 Mar 2019 14:44:33 -0600 [thread overview]
Message-ID: <CAHmME9pfdqfW_7+_vWcN-YJcJcG7hFpBWpw8251Y_Nv5v5FxFg@mail.gmail.com> (raw)
In-Reply-To: <20190313185259.GA4579@wolff.to>
On Wed, Mar 13, 2019 at 12:53 PM Bruno Wolff III <bruno@wolff.to> wrote:
> I got something that seems to be working. So I'm good until the real fixes
> are ready.
Perhaps your [fake?!] fixes could become the real fixes if you ran
`git send-email` to the mailing list?
Jason
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-03-13 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 18:38 Bruno Wolff III
2019-03-13 18:52 ` Bruno Wolff III
2019-03-13 20:44 ` Jason A. Donenfeld [this message]
2019-03-14 4:08 ` Bruno Wolff III
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=CAHmME9pfdqfW_7+_vWcN-YJcJcG7hFpBWpw8251Y_Nv5v5FxFg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=bruno@wolff.to \
--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).