From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Ankur Kothari <ankur@lipidity.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] wg-quick: Fix alternate routing table syntax on OpenBSD
Date: Mon, 5 Aug 2019 20:46:57 +0200 [thread overview]
Message-ID: <CAHmME9pGLM9a3Ww-MNy7mNT6JEQQXv4qLF0LDrAqVFUbDDPrsg@mail.gmail.com> (raw)
In-Reply-To: <20190720122016.57765-1-ankur@lipidity.com>
Hi Ankur,
Thanks for this. Could you provide your Signed-off-by line? Also, why
is this required? Is this a recent change in syntax? A new syntax? Was
the syntax always wrong? What's the deal?
Thanks,
Jason
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-08-05 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 12:20 [PATCH] wg-quick: Fix alternate routing table syntax on OpenBSD Ankur Kothari
2019-08-05 18:46 ` Jason A. Donenfeld [this message]
2019-08-05 19:13 ` Janne Johansson
2019-08-05 19:38 ` Jason A. Donenfeld
2019-08-05 22:57 ` [PATCH v2] wg-quick: openbsd: fix alternate routing table syntax Ankur Kothari
2019-08-07 8:41 ` 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=CAHmME9pGLM9a3Ww-MNy7mNT6JEQQXv4qLF0LDrAqVFUbDDPrsg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=ankur@lipidity.com \
--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).