From: Thomas Monjalon <thomas@monjalon.net>
To: David Hunt <david.hunt@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc/contrib: patch and code in same file
Date: Sat, 24 Nov 2018 21:48:38 +0100 [thread overview]
Message-ID: <1560116.2faodLGoI7@xps> (raw)
In-Reply-To: <c668f348-d894-09e0-65c0-e32ea33f8c80@intel.com>
26/10/2018 13:37, Ferruh Yigit:
> On 10/26/2018 10:37 AM, David Hunt wrote:
> > Add a paragraph to the patch contribution guide suggesting that developers
> > keep doc updates in the same patch as the code, rather than one big
> > doc update as the final patch in a patch set.
> >
> > Signed-off-by: David Hunt <david.hunt@intel.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied with following title:
doc: suggest to keep doc and code in same patch
prev parent reply other threads:[~2018-11-24 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 9:37 David Hunt
2018-10-26 11:37 ` Ferruh Yigit
2018-11-24 20:48 ` Thomas Monjalon [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=1560116.2faodLGoI7@xps \
--to=thomas@monjalon.net \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.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).