From: "Yigit, Ferruh" <ferruh.yigit@linux.intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] maintainers: add git repo information for libraries
Date: Wed, 20 Nov 2019 13:47:02 +0000 [thread overview]
Message-ID: <53e4b9e0-6c37-0e47-df30-f45b081256a6@linux.intel.com> (raw)
In-Reply-To: <1776490.q62YuOiO2q@xps>
On 3/13/2019 7:35 AM, Thomas Monjalon wrote:
> 13/03/2019 02:59, Ferruh Yigit:
>> Add target git sub-tree information for libraries, this is mainly to
>> reduce apply failures of the patches by automating target sub-tree
>> selection for a patch for automation.
>>
>> Also can be useful for developers to define which tree to base their
>> patches for specific library.
>>
>> Plan for DPDK Community lab is always try the main repo first, if patch
>> fails to apply, detect and try on that detected sub-tree. This is to
>> cover the case where sub-tree and main repo diverged and patch is based
>> on sub-tree.
>> Both because of above usage and to not create noise in file, git tree
>> information is not added for libraries which target main repo, which is
>> taken as default git repo.
>
> I think adding tree info for PMDs is redundant.
> Can we improve the script to smartly retrieve PMD tree,
> based on the T: line at the beginning of the PMD section?
>
>
As far as I know script has been updated to work without this patch, so updating
this patch status as rejected.
prev parent reply other threads:[~2019-11-20 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 1:59 Ferruh Yigit
2019-03-13 7:35 ` Thomas Monjalon
2019-11-20 13:47 ` Yigit, Ferruh [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=53e4b9e0-6c37-0e47-df30-f45b081256a6@linux.intel.com \
--to=ferruh.yigit@linux.intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).