DPDK patches and discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: dev@dpdk.org, "Morten Brørup" <mb@smartsharesystems.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: Re: Depends-on
Date: Mon, 03 Jun 2024 14:48:12 -0400	[thread overview]
Message-ID: <f7tv82p2783.fsf@redhat.com> (raw)
In-Reply-To: <CAJvnSUB+eADEwSg00PN4HkFMeTQzWLQeNcBsqXnBSvQEP3S8-A@mail.gmail.com> (Patrick Robb's message of "Fri, 31 May 2024 17:22:39 -0400")

Patrick Robb <probb@iol.unh.edu> writes:

> *
> Hi all,
>
> Found my way to this thread based on the CI testing call yesterday, as I am about to put
> together the blurb for the dpdk website testing page that documents support (or lack
> thereof) for depends-on in CI. 

Thanks.

> On Wed, May 29, 2024 at 10:40 AM Morten Brørup <mb@smartsharesystems.com> wrote:
>
>  > From: Aaron Conole [mailto:aconole@redhat.com]
>  > Sent: Wednesday, 29 May 2024 16.34
>
>  > 
>  > I'll try to spend some time and add patch based support, but I think
>  > there was some weird tricky stuff going on.
>
>  Series support suffices for this patch, so figuring out what is wrong with that will make
>  me happy. :-)
>
> It probably doesn't make sense to add depends on individual patch support, as the PW
> maintainer and Thomas agreed on depends on series support only going forward. 
>
> https://github.com/getpatchwork/git-pw/issues/71#issuecomment-1938927101


      reply	other threads:[~2024-06-03 18:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 11:06 Depends-on Morten Brørup
2024-05-29 14:33 ` Depends-on Aaron Conole
2024-05-29 14:40   ` Depends-on Morten Brørup
2024-05-31 21:22     ` Depends-on Patrick Robb
2024-06-03 18:48       ` Aaron Conole [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=f7tv82p2783.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=probb@iol.unh.edu \
    --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).