All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Serhey Popovych <serhe.popovych@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next 1/4] bridge: implement json pretty print flag
Date: Tue, 20 Feb 2018 11:17:56 -0800	[thread overview]
Message-ID: <20180220111756.2204699c@xeon-e3> (raw)
In-Reply-To: <86ffe1d0-a82c-26d7-3144-b9116f5d211e@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 290 bytes --]

On Tue, 20 Feb 2018 00:24:46 +0200
Serhey Popovych <serhe.popovych@gmail.com> wrote:

> While new_json_obj() from json_print.c isn't used in bridge/ it is still
> seems reasonable in my opinion to use common @pretty variable.

Actually new_json_obj is used in later patches 2 and 3.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-02-20 19:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19  3:18 [PATCH iproute2-next 0/4] bridge: json and color output Stephen Hemminger
2018-02-19  3:18 ` [PATCH iproute2-next 1/4] bridge: implement json pretty print flag Stephen Hemminger
2018-02-19 22:24   ` Serhey Popovych
2018-02-20 19:17     ` Stephen Hemminger [this message]
2018-02-19  3:18 ` [PATCH iproute2-next 2/4] bridge: colorize output and use JSON print library Stephen Hemminger
2018-02-19  3:18 ` [PATCH iproute2-next 3/4] bridge: add json support for link command Stephen Hemminger
2018-02-19  3:18 ` [PATCH iproute2-next 4/4] bridge: update man page for new color and json changes Stephen Hemminger

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=20180220111756.2204699c@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    --cc=serhe.popovych@gmail.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.