From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Sean Morrissey <sean.morrissey@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] devtools: export title syntax for check-git-log
Date: Fri, 25 Oct 2019 14:44:21 +0100 [thread overview]
Message-ID: <5bd4bae7-9fc8-a819-ac85-d067fa1b9d7d@intel.com> (raw)
In-Reply-To: <20191025095957.29632-1-sean.morrissey@intel.com>
On 10/25/2019 10:59 AM, Sean Morrissey wrote:
> Moved title syntax to a separate file so that it improves code readability
> and allows for easy addition of new correct title syntax in future cases.
>
> Signed-off-by: Sean Morrissey <sean.morrissey@intel.com>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2019-10-25 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 9:59 Sean Morrissey
2019-10-25 13:44 ` Ferruh Yigit [this message]
2020-02-22 20:38 ` Thomas Monjalon
2020-02-24 12:02 ` [dpdk-dev] [PATCH v2] devtools: export title syntax data " Ferruh Yigit
2020-02-24 13:39 ` Thomas Monjalon
2020-02-24 14:38 ` Ferruh Yigit
2020-02-24 15:30 ` [dpdk-dev] [PATCH v3] " Ferruh Yigit
2020-02-25 20: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=5bd4bae7-9fc8-a819-ac85-d067fa1b9d7d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=sean.morrissey@intel.com \
--cc=thomas@monjalon.net \
/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).