From: Thomas Monjalon <thomas@monjalon.net>
To: Muhammad Bilal <m.bilal@emumba.com>
Cc: marko.kovacevic@intel.com, john.mcnamara@intel.com,
stable@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] doc/guides/contributing/patches.rst: corrected typing mistake in line 185
Date: Sun, 24 May 2020 23:37:18 +0200 [thread overview]
Message-ID: <2669583.3DfjT8CoTR@thomas> (raw)
In-Reply-To: <20200326054654.9483-1-m.bilal@emumba.com>
26/03/2020 06:46, Muhammad Bilal:
> Bugzilla ID: 422
> Cc: marko.kovacevic@intel.com
> Cc: john.mcnamara@intel.com
> Cc: dev@dpdk.org
> Cc: stable@dpdk.org
> Signed-off-by: Muhammad Bilal <m.bilal@emumba.com>
> ---
> --- a/doc/guides/contributing/patches.rst
> +++ b/doc/guides/contributing/patches.rst
> -file as the code, rather than one big documentation patch at then end of a
> +file as the code, rather than one big documentation patch at the end of a
Fixes: 9e0e4a00df77 ("doc: suggest to keep doc and code in same patch")
Applied, thanks
prev parent reply other threads:[~2020-05-24 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 5:46 Muhammad Bilal
2020-05-24 21:37 ` 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=2669583.3DfjT8CoTR@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=m.bilal@emumba.com \
--cc=marko.kovacevic@intel.com \
--cc=stable@dpdk.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).