From: Phil Sutter <phil@nwl.cc>
To: Matteo Croce <mcroce@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2] netns: avoid directory traversal (was: ip netns: Make sure netns name is sane)
Date: Thu, 20 Jul 2017 09:44:10 +0200 [thread overview]
Message-ID: <20170720074410.GG16375@orbyte.nwl.cc> (raw)
In-Reply-To: <20170719223632.4124-1-mcroce@redhat.com>
Hi Matteo,
I don't think git-am understands the subject change semantics you use
here, so please drop the '(was: ...)' part from it.
On Thu, Jul 20, 2017 at 12:36:32AM +0200, Matteo Croce wrote:
> v2: reword commit message
In my opinion, this belongs to patch meta info (below the three-dashes
line), not the commit message.
Please put the maintainer in Cc when submitting patches. It helps them
to keep track of it. This counts for all upstream projects, not just
iproute2.
Thanks, Phil
next prev parent reply other threads:[~2017-07-20 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 12:08 [PATCH] netns: avoid directory traversal (was: ip netns: Make sure netns name is sane) Matteo Croce
2017-07-10 13:07 ` Phil Sutter
2017-07-19 0:12 ` Stephen Hemminger
2017-07-19 22:36 ` [PATCH v2] " Matteo Croce
2017-07-20 7:44 ` Phil Sutter [this message]
2017-07-21 0:25 ` 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=20170720074410.GG16375@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=mcroce@redhat.com \
--cc=netdev@vger.kernel.org \
/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).