From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Haller <thaller@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/4] iprule: avoid printing extra space after gateway for nat action
Date: Wed, 24 Apr 2019 15:14:06 -0700 [thread overview]
Message-ID: <20190424151406.2fdbf4af@hermes.lan> (raw)
In-Reply-To: <20190423071615.19729-1-thaller@redhat.com>
On Tue, 23 Apr 2019 09:16:12 +0200
Thomas Haller <thaller@redhat.com> wrote:
> For all other actions we avoid the trailing space, so do it here
> as well.
>
> Signed-off-by: Thomas Haller <thaller@redhat.com>
Looks good, applied all 4 patches.
prev parent reply other threads:[~2019-04-24 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 7:16 [PATCH 1/4] iprule: avoid printing extra space after gateway for nat action Thomas Haller
2019-04-23 7:16 ` [PATCH 2/4] iprule: avoid trailing space in print_rule() after printing protocol Thomas Haller
2019-04-23 7:16 ` [PATCH 3/4] iprule: refactor print_rule() to use leading space before printing attribute Thomas Haller
2019-04-23 7:16 ` [PATCH 4/4] iprule: always print realms keyword for rule Thomas Haller
2019-04-24 22:14 ` 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=20190424151406.2fdbf4af@hermes.lan \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=thaller@redhat.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).