From: Bruce Richardson <bruce.richardson@intel.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: Ferruh Yigit <ferruh.yigit@amd.com>,
Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>, <dev@dpdk.org>,
Aaron Conole <aconole@redhat.com>,
Michael Santana <maicolgabriel@hotmail.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Raslan Darawsheh <rasland@nvidia.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: Re: [PATCH] version: 24.03-rc0
Date: Fri, 1 Dec 2023 17:32:55 +0000 [thread overview]
Message-ID: <ZWoYx9qbuxhuLgt2@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAJvnSUCcbcZjeGLB9KRkYsYmH-2Fvq2cHpN5CHRGuK84_yTc5g@mail.gmail.com>
On Fri, Dec 01, 2023 at 12:24:12PM -0500, Patrick Robb wrote:
> On Fri, Dec 1, 2023 at 11:36 AM Ferruh Yigit <[1]ferruh.yigit@amd.com>
> wrote:
>
> On 12/1/2023 2:30 PM, Bruce Richardson wrote:
> > On Fri, Dec 01, 2023 at 11:33:25AM +0000, Ferruh Yigit wrote:
> >> On 12/1/2023 11:13 AM, Bruce Richardson wrote:
> >>> On Fri, Dec 01, 2023 at 09:04:10AM +0100, Thomas Monjalon wrote:
> >>>> 30/11/2023 19:33, Patrick Robb:
> >>>>> On Thu, Nov 30, 2023 at 4:24 AM David Marchand
> <[2]david.marchand@redhat.com>
> >>>>> wrote:
> >>>>>
> >>>>>> What it means:
> >>>>>> - for the [3]https://dpdk.org/git/dpdk repository, all the
> branches and
> >>>>>> tags are mirrored to [4]https://github.com/DPDK/dpdk as it
> was done so
> >>>>>> far,
> >>>>>> - for the [5]https://git.dpdk.org/next/dpdk-next-*
> repositories, only
> >>>>>> branches named "main", "staging" or "for-*" are mirrored to
> >>>>>> [6]https://github.com/DPDK/dpdk with a prefix.
> >>>>>
> >>>>> Thank you David for clearing some of this up on the CI testing
> meeting. I
> >>>>> think the final loose end was you were wondering which
> branches within the
> >>>>> next-* repos we were running from. I'll paste that below:
> >>>>>
> >>>>> dpdk-next-crypto: for-main
> >>>>> dpdk-next-eventdev: for-main
> >>>>> dpdk-next-net: main
> >>>>> dpdk-next-net-brcm: main
> >>>>> dpdk-next-net-intel: main
> >>>>> dpdk-next-net-mlx: main
> >>>>> dpdk-next-net-mrvl: for-next-net
> >>>>> dpdk-next-virtio: main
> >>>>> dpdk-next-baseband: for-main
> >>>>
> >>>> We should test patches on top of the branch which is validated
> >>>> by the tree maintainer and ready to pull.
> >>>> This is the default branch (HEAD) of its repository on
> [7]dpdk.org.
> >>>> This is the list of equivalent GitHub branches to use for
> testing:
> >>>>
> >>>> main
> >>>> next-baseband-for-main
> >>>> next-crypto-for-main
> >>>> next-eventdev-for-main
> >>>> next-net-for-main-repo
> >>>
> >>> The (slight) inconsistency here is curious. Is there a reason
> why this
> >>> branch has "repo" on the end and none of the others don't?
> >>>
> >>
> >> No specific reason, it started like that in the past. If the
> consensus
> >> is to go with 'for-main', I can update it.
> >>
> > In all likelihood it's not a big deal.
> >
> > I'm just thinking that for any future automation or tracking,
> having a very
> > consistent naming would be best. For example, in the one-liner I
> posted for
> > generating the graph showing the inter-tree flow, I needed a
> special regex
> > to strip off the "-repo", so that we didn't have a separate target
> called
> > "main-repo" and another called "main".
> >
> Agree on above, created 'for-main' branch and will use it now.
> But I need help from Thomas/David to delete remote 'for-main-repo'
> branch.
>
> Great. So for CI testing, we will use dpdk-*-for-main when possible.
> next-virtio only has for-next-net and staging, so we will use
> for-next-net, unless we want to rename that one too to have a true
> standard.
That one is correct, because next-virtio doesn't go straight to main. There
will soon similarly be next-net-intel-for-next-net, for example, for the
other sub-trees that get pulled into next-net.
/Bruce
next prev parent reply other threads:[~2023-12-01 17:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 16:18 David Marchand
2023-11-30 9:23 ` David Marchand
2023-11-30 9:30 ` Ferruh Yigit
2023-11-30 9:32 ` David Marchand
2023-11-30 9:53 ` David Marchand
2023-11-30 10:05 ` Ferruh Yigit
2023-11-30 18:33 ` Patrick Robb
2023-12-01 8:04 ` Thomas Monjalon
2023-12-01 8:55 ` David Marchand
2023-12-01 10:32 ` Thomas Monjalon
2023-12-01 10:39 ` David Marchand
2023-12-01 11:13 ` Bruce Richardson
2023-12-01 11:33 ` Ferruh Yigit
2023-12-01 14:30 ` Bruce Richardson
2023-12-01 16:36 ` Ferruh Yigit
2023-12-01 17:24 ` Patrick Robb
2023-12-01 17:32 ` Bruce Richardson [this message]
2023-12-01 21:08 ` Thomas Monjalon
2023-12-01 21:24 ` Patrick Robb
2023-12-07 9:55 ` David Marchand
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=ZWoYx9qbuxhuLgt2@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aconole@redhat.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=maicolgabriel@hotmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=probb@iol.unh.edu \
--cc=qi.z.zhang@intel.com \
--cc=rasland@nvidia.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).