From: Thomas Monjalon <thomas@monjalon.net>
To: Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] doc: add guides for patch fix issues
Date: Tue, 29 May 2018 17:24:43 +0200 [thread overview]
Message-ID: <6140320.jqdv53SyBi@xps> (raw)
In-Reply-To: <20180529110124.35666-1-marko.kovacevic@intel.com>
29/05/2018 13:01, Marko Kovacevic:
> 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>
Applied, thanks.
Note: I have re-wrapped the text below:
> +`Bugzilla <https://dpdk.org/tracker>`_
> +is a bug- or issue-tracking system. Bug-tracking
> +systems allow individual or groups of developers effectively to keep track of outstanding
> +problems with their product. When fixing an issue raised in Bugzilla, the patch must contain
> +a Bugzilla issue ID in the body of the commit message. For example::
to be more logically split:
+`Bugzilla <https://dpdk.org/tracker>`_
+is a bug- or issue-tracking system.
+Bug-tracking systems allow individual or groups of developers
+effectively to keep track of outstanding problems with their product.
+When fixing an issue raised in Bugzilla, the patch must contain
+a Bugzilla issue ID in the body of the commit message.
+For example::
It think such wrapping should be preferred because it allows to change
or remove a sentence without disturbing the other ones.
prev parent reply other threads:[~2018-05-29 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 15:23 [dpdk-dev] [PATCH v1] " Marko Kovacevic
2018-05-28 15:53 ` Ferruh Yigit
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 [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=6140320.jqdv53SyBi@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).