[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180109081237.38e6cd1b@xeon-e3>
Date: Tue, 9 Jan 2018 08:12:37 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: Serhey Popovych <serhe.popovych@...il.com>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH iproute2 0/7] ip6/tunnel: Unify tclass, flowlabel and
encap_limit output
On Mon, 8 Jan 2018 19:06:31 +0200
Serhey Popovych <serhe.popovych@...il.com> wrote:
> With this series I want to improve printing of tclass,
> flowlabel and encapsulation limit (encap_limit) options.
>
> Everything within this series is open for your comments,
> suggestions and criticism.
>
> See individual patch description message for details.
>
> Thanks,
> Serhii
>
> Serhey Popovych (7):
> ip6/tunnel: Fix tclass output
> ip6tnl/tunnel: Do not print obscure flowinfo
> ip6/tunnel: Unify tclass printing
> ip6/tunnel: Unify flowlabel printing
> ip6/tunnel: Unify encap_limit printing
> gre6/tunnel: Output flowlabel after tclass
> ip6tnl/tunnel: Output hoplimit before encapsulation limit
>
> ip/link_gre6.c | 54 ++++++++++++++++------------------------------
> ip/link_ip6tnl.c | 63 ++++++++++++++++++------------------------------------
> 2 files changed, 40 insertions(+), 77 deletions(-)
>
I am confused. this patch series arrived after the v3 version.
Which one is correct?
Also when sending multiple versions of a patch series is it is
best practice to include a revision history in the cover letter like:
v2
ip6/tunnel - incorporate review feedback in fou
v3
ip/gre - fix spelling errors
Powered by blists - more mailing lists