From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Marko Kovacevic <marko.kovacevic@intel.com>, dev@dpdk.org
Cc: john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v1] doc: add guides for patch fix issues
Date: Mon, 28 May 2018 16:53:33 +0100 [thread overview]
Message-ID: <ce40dfa9-5cd7-0ee7-cf42-6fb247b70bae@intel.com> (raw)
In-Reply-To: <20180528152342.22467-1-marko.kovacevic@intel.com>
On 5/28/2018 4:23 PM, Marko Kovacevic wrote:
> Added contribution guideline for adding tags
> when sending patches that have been raised on
> Bugzilla
>
> Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2018-05-28 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 15:23 Marko Kovacevic
2018-05-28 15:53 ` Ferruh Yigit [this message]
2018-05-29 10:32 ` Thomas Monjalon
2018-05-29 10:45 ` Kovacevic, Marko
2018-05-29 11:01 ` [dpdk-dev] [PATCH v2] " Marko Kovacevic
2018-05-29 15:24 ` Thomas Monjalon
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=ce40dfa9-5cd7-0ee7-cf42-6fb247b70bae@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@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).