DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: David Marchand <david.marchand@redhat.com>,
	Patrick Robb <probb@iol.unh.edu>, <dev@dpdk.org>,
	Aaron Conole <aconole@redhat.com>,
	Michael Santana <maicolgabriel@hotmail.com>,
	Ferruh Yigit <ferruh.yigit@amd.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 11:13:08 +0000	[thread overview]
Message-ID: <ZWm_xK_QfcDxJ5QV@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <7128906.ZaRXLXkqSa@thomas>

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 <david.marchand@redhat.com>
> > wrote:
> > 
> > > What it means:
> > > - for the https://dpdk.org/git/dpdk repository, all the branches and
> > > tags are mirrored to https://github.com/DPDK/dpdk as it was done so
> > > far,
> > > - for the https://git.dpdk.org/next/dpdk-next-* repositories, only
> > > branches named "main", "staging" or "for-*" are mirrored to
> > > 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 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?

> 	next-net-brcm-for-next-net
> 	next-net-intel-for-next-net
> 	next-net-mlx-for-next-net
> 	next-net-mrvl-for-main
> 	next-virtio-for-next-net
> 

We can also use this to produce nice graphs showing the flow through trees
if we want. This works for me as basic graph, but can probably be cleaned
up more:

git branch -a | awk 'BEGIN {print "digraph {"} $1 ~ /-for-/ {sub(/remotes.origin./, "", $1); sub(/-repo/,"", $1); sub(/-for-/,"\" -> \"", $1); print "\""$1"\""} END {print "}"}' | dot -Tpng -o trees.png

/Bruce

  parent reply	other threads:[~2023-12-01 11:13 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 [this message]
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
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=ZWm_xK_QfcDxJ5QV@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).