From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
ci@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-ci] [PATCH] doc: add dependency syntax to contributing guide
Date: Fri, 3 Jul 2020 10:03:35 +0100 [thread overview]
Message-ID: <9e0187ba-dfce-c446-c950-2daed35055b7@intel.com> (raw)
In-Reply-To: <2130699.hsn6GWqRH1@thomas>
On 7/3/2020 10:01 AM, Thomas Monjalon wrote:
> 02/07/2020 18:13, Ferruh Yigit:
>> On 7/1/2020 12:59 PM, Thomas Monjalon wrote:
>>> 01/07/2020 13:35, Ferruh Yigit:
>>>> To help managing patch dependencies, both for maintainers or automation
>>>> tasks, document a syntax for commit logs or cover letters to express
>>>> their dependencies.
>>>>
>>>> Using the syntax proposed in Bugzilla ID 210:
>>>> [https://bugs.dpdk.org/show_bug.cgi?id=210]
>>>>
>>>> 'Depends-on: series-NNNNN' OR 'Depends-on: patch-NNNNN'
>>>
>>> It would be more convenient to add the patch or series title
>>> as we do for "Fixes" tag:
>>>
>>> Depends-on: series-NNNNN ("Title of the series")
>>
>> OK, will update in next version.
>>
>> Should we enforce any location for the tag, like first of line of the commit log
>> or cover letter? Does something like this helps to parsers?
>
> It should be in cover letter if there is one.
> If no cover letter, I would prefer not having it in git,
+1
> so I would suggest having a line of --- before.
OK
next prev parent reply other threads:[~2020-07-03 9:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 11:35 Ferruh Yigit
2020-07-01 11:59 ` Thomas Monjalon
2020-07-02 16:13 ` Ferruh Yigit
2020-07-03 9:01 ` Thomas Monjalon
2020-07-03 9:03 ` Ferruh Yigit [this message]
2020-07-03 9:53 ` [dpdk-ci] [PATCH v2] " Ferruh Yigit
2020-07-06 15:09 ` Aaron Conole
2020-07-06 15:12 ` Thomas Monjalon
2020-07-06 18:02 ` Aaron Conole
2020-07-30 23:13 ` [dpdk-ci] [dpdk-dev] " 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=9e0187ba-dfce-c446-c950-2daed35055b7@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@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).