DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] maintainers: set git tree for EAL and core libraries
Date: Wed, 22 Jan 2020 23:07:40 +0100	[thread overview]
Message-ID: <121518814.NQWE8gLqXz@xps> (raw)
In-Reply-To: <20200120203513.10148-1-david.marchand@redhat.com>

20/01/2020 21:35, David Marchand:
> Without a git tree, the "guess" script from dpdk-ci will ignore all files
> that are referenced in those sections and let a patchset land in any
> subtree.
> Changes in the EAL, mbuf, mempool... go through the main repository.
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>

Acked-by: Thomas Monjalon <thomas@monjalon.net>

Note: this is needed because of this change in our tooling:
http://git.dpdk.org/tools/dpdk-ci/commit/?id=fb8eab4f89333

Applied, thanks



      reply	other threads:[~2020-01-22 22:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 20:35 David Marchand
2020-01-22 22:07 ` 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=121518814.NQWE8gLqXz@xps \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    /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).