patches for DPDK stable branches
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: dpdk stable <stable@dpdk.org>, Luca Boccassi <bluca@debian.org>,
	 Thomas Monjalon <thomas@monjalon.net>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-stable] [PATCH stable master] README: indicate master branch is not used
Date: Wed, 11 Mar 2020 12:33:18 +0100	[thread overview]
Message-ID: <CAJFAV8zJHdXkycPGns6j+MmrBM0ROj9aMG=VFPmMGyRQoyx1Nw@mail.gmail.com> (raw)
In-Reply-To: <20200311112039.32038-1-ktraynor@redhat.com>

On Wed, Mar 11, 2020 at 12:21 PM Kevin Traynor <ktraynor@redhat.com> wrote:
>
> There has been a commit history on the dpdk-stable repo
> master branch even though it is not actively used or really
> defined what should be there. This is the default branch when
> cloning the repo so it can be confusing.
>
> Drop all history on dpdk-stable repo master branch back to the
> initial commit and add to the existing README blurb that
> stable/LTS branches should be used.
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>

Acked-by: David Marchand <david.marchand@redhat.com>


-- 
David Marchand


  parent reply	other threads:[~2020-03-11 11:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 11:20 Kevin Traynor
2020-03-11 11:26 ` Luca Boccassi
2020-03-11 11:33 ` David Marchand [this message]
2020-03-11 13:12 ` Thomas Monjalon
2020-03-11 13:45   ` Kevin Traynor
2020-03-11 13:53 ` [dpdk-stable] [PATCH stable master v2] " Kevin Traynor
2020-03-11 14:02   ` Thomas Monjalon
2020-03-11 14:05     ` Kevin Traynor
2020-03-12 11:14     ` Kevin Traynor

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='CAJFAV8zJHdXkycPGns6j+MmrBM0ROj9aMG=VFPmMGyRQoyx1Nw@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=bluca@debian.org \
    --cc=ferruh.yigit@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=stable@dpdk.org \
    --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).