DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: dev@dpdk.org, thomas@monjalon.net,
	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: Thu, 30 Nov 2023 10:32:28 +0100	[thread overview]
Message-ID: <CAJFAV8xifg24VRuJ5_S+K2zJ-mGD=SsLqL_6obyBYkoVfnceSg@mail.gmail.com> (raw)
In-Reply-To: <20cb8610-103a-4504-a349-31ed8777053a@amd.com>

On Thu, Nov 30, 2023 at 10:30 AM Ferruh Yigit <ferruh.yigit@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.marchand@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.marchand@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_xXQ@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


  reply	other threads:[~2023-11-30  9:32 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 [this message]
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
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='CAJFAV8xifg24VRuJ5_S+K2zJ-mGD=SsLqL_6obyBYkoVfnceSg@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --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=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).