From: David Miller <davem@davemloft.net>
To: kurup.manish@gmail.com
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
jakub.kicinski@netronome.com,
pieter.jansenvanvuuren@netronome.com, simon.horman@netronome.com,
john.hurley@netronome.com, aring@mojatatu.com, mrv@mojatatu.com,
manish.kurup@verizon.com, netdev@vger.kernel.org,
oss-drivers@netronome.com
Subject: Re: [PATCH net-next v6 0/3] Incorporated all required changes
Date: Tue, 07 Nov 2017 08:45:35 +0900 (KST) [thread overview]
Message-ID: <20171107.084535.1468386023963515204.davem@davemloft.net> (raw)
In-Reply-To: <CAJrKpLaNX4gX0yTkKkRvmU=Ti3xYGkoEu4cAcDhwnZF2tZU1SA@mail.gmail.com>
From: Manish Kurup <kurup.manish@gmail.com>
Date: Mon, 6 Nov 2017 11:52:37 -0500
> Currently, the body of the commit message describes what it is doing
> in each commit patch. Would you like me to add some detail to the
> description of each commit?
This is not what I am asking for.
The header posting for a patch series serves a very important
purpose. It tells the reader at a high level what the patch
series is doing as a whole, how it is doing it, and why it is
doing it that way.
prev parent reply other threads:[~2017-11-06 23:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 15:49 [PATCH net-next v6 0/3] Incorporated all required changes Manish Kurup
2017-11-05 13:08 ` David Miller
[not found] ` <CAJrKpLaNX4gX0yTkKkRvmU=Ti3xYGkoEu4cAcDhwnZF2tZU1SA@mail.gmail.com>
2017-11-06 18:25 ` Pieter Jansen van Vuuren
2017-11-06 23:45 ` David Miller [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=20171107.084535.1468386023963515204.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aring@mojatatu.com \
--cc=jakub.kicinski@netronome.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.hurley@netronome.com \
--cc=kurup.manish@gmail.com \
--cc=manish.kurup@verizon.com \
--cc=mrv@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=pieter.jansenvanvuuren@netronome.com \
--cc=simon.horman@netronome.com \
--cc=xiyou.wangcong@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 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).