From: Stephen Hemminger <stephen@networkplumber.org>
To: Benedict Wong <benedictwong@google.com>
Cc: netdev@vger.kernel.org, "Nathan Harold" <nharold@google.com>,
"Lorenzo Colitti" <lorenzo@google.com>,
"Maciej Żenczykowski" <maze@google.com>
Subject: Re: [RFC iproute2] xfrm: add option to hide keys in state output
Date: Mon, 7 Jan 2019 12:50:01 -0800 [thread overview]
Message-ID: <20190107125001.07df5a1a@hermes.lan> (raw)
In-Reply-To: <CANrj0bbTWY5Zm5UiSSykSSkzG55ajkV6wfj2gGKGzaeGht9N9A@mail.gmail.com>
On Mon, 7 Jan 2019 12:37:41 -0800
Benedict Wong <benedictwong@google.com> wrote:
> Noted. Should I wait until xfrm is converted to JSON output formatting?
>
> Or if there are no structural and stylistic issues, should I re-send
> this as a patch?
>
No the patch should go in now.
prev parent reply other threads:[~2019-01-07 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 23:19 [RFC iproute2] xfrm: add option to hide keys in state output Benedict Wong
2019-01-05 0:20 ` Stephen Hemminger
2019-01-07 20:37 ` Benedict Wong
2019-01-07 20:50 ` Stephen Hemminger [this message]
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=20190107125001.07df5a1a@hermes.lan \
--to=stephen@networkplumber.org \
--cc=benedictwong@google.com \
--cc=lorenzo@google.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=nharold@google.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).