01/12/2023 09:55, David Marchand: > On Fri, Dec 1, 2023 at 9:04 AM Thomas Monjalon <tho...@monjalon.net> wrote: > > > > 30/11/2023 19:33, Patrick Robb: > > > On Thu, Nov 30, 2023 at 4:24 AM David Marchand <david.march...@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 could be queried to avoid maintaining a map that may change in the > future. > > Some (pinpointed) query like below should not be that heavy to > dpdk.org git server: > $ git ls-remote --symref https://dpdk.org/git/next/dpdk-next-net HEAD > ref: refs/heads/for-main-repo HEAD > afe986d15845e7a774ae3a4e23e03bb7d3bcba72 HEAD
Yes > This could be added as a new script in dpdk-ci. > Like tools/get_mirror.py which would parse MAINTAINERS and send this > query I mentionned above? > > $ tools/pw_maintainers_cli.py --type series list-trees 30419 > dpdk-next-net > > $ tools/get_mirror.py dpdk-next-net > https://github.com/DPDK/dpdk next-net-for-main-repo Why not adding it to pw_maintainers_cli.py? It could be an option to get the GitHub branch. > > 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 > > 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
