From: Stephen Hemminger <shemming@brocade.com>
To: Phil Sutter <phil@nwl.cc>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>, <netdev@vger.kernel.org>
Subject: Re: [iproute PATCH 2/8] tc: connmark, pedit: Rename BRANCH to CONTROL
Date: Mon, 21 Mar 2016 12:08:23 -0700 [thread overview]
Message-ID: <20160321120823.5ec44d28@xeon-e3> (raw)
In-Reply-To: <1458165384-900-3-git-send-email-phil@nwl.cc>
On Wed, 16 Mar 2016 22:56:18 +0100
Phil Sutter <phil@nwl.cc> wrote:
> As Jamal suggested, BRANCH is the wrong name, as these keywords go
> beyond simple branch control - e.g. loops are possible, too. Therefore
> rename the non-terminal to CONTROL instead which should be more
> appropriate.
>
> Signed-off-by: Phil Sutter <phil@nwl.cc>
The series no longer applies cleanly after my cleanups.
Please resubmit
next prev parent reply other threads:[~2016-03-21 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 21:56 [iproute PATCH 0/8] Follow-up to my action man pages series Phil Sutter
2016-03-16 21:56 ` [iproute PATCH 1/8] doc/tc-filters.tex: Drop overly subjective paragraphs Phil Sutter
2016-03-16 21:56 ` [iproute PATCH 2/8] tc: connmark, pedit: Rename BRANCH to CONTROL Phil Sutter
2016-03-21 19:08 ` Stephen Hemminger [this message]
2016-03-16 21:56 ` [iproute PATCH 3/8] man: tc-csum.8: Add an example Phil Sutter
2016-03-16 21:56 ` [iproute PATCH 4/8] man: tc-mirred.8: Reword man page a bit, add generic mirror example Phil Sutter
2016-03-16 21:56 ` [iproute PATCH 5/8] man: tc-police.8: Emphasize on the two rate control mechanisms Phil Sutter
2016-03-16 21:56 ` [iproute PATCH 6/8] man: tc-skbedit.8: Elaborate a bit on TX queues Phil Sutter
2016-03-16 21:56 ` [iproute PATCH 7/8] tc/m_vlan.c: mention CONTROL option in help text Phil Sutter
2016-03-16 21:56 ` [iproute PATCH 8/8] man: tc-vlan.8: Describe CONTROL option Phil Sutter
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=20160321120823.5ec44d28@xeon-e3 \
--to=shemming@brocade.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
/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).