On Thu, Nov 30, 2023 at 10:30 AM Ferruh Yigit <ferruh.yi...@amd.com> wrote: > > On 11/30/2023 9:23 AM, David Marchand wrote: > > On Wed, Nov 29, 2023 at 5:20 PM David Marchand > > <david.march...@redhat.com> wrote: > >> > >> Start a new release cycle with empty release notes. > >> Bump version and ABI minor. > >> Bump libabigail from 2.1 to 2.4 and enable ABI checks. > >> > >> Signed-off-by: David Marchand <david.march...@redhat.com> > > > > Applied, thanks. > > > > Copying subtree maintainers, and ci@ mailing list. > > As a result of the discussion on the ci ml > > (http://inbox.dpdk.org/ci/cajvnsub2zxmhcdzc4rlrurm75myohjuwfuttk8gnvredfp_...@mail.gmail.com/T/#t), > > we worked on setting up some automatic mirroring of dpdk.org > > repositories to the github DPDK repository. > > > > > > 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. > > One example: changes to the for-main branch of the dpdk-next-crypto > > repo will be mirrored to a github branch next-crypto-for-main > > > > > > For subtree maintainers. > > > > It should change nothing to you guys. > > Please rebase your trees on v24.03-rc0 and push it to dpdk.org. > > And then double check that the mirror happened (looking at git push > > output, and checking https://github.com/DPDK/dpdk/branches). > > If you hit some issue, ping me. > > > > I force push a lot, is mirroring configured to cope with this?
It is supposed to be handled, yes. -- David Marchand
