DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] development/integration branch?
Date: Wed, 22 Oct 2014 08:54:49 -0700	[thread overview]
Message-ID: <F5F8A6AD-9A22-4C6B-AA47-3DC509685254@mhcomputing.net> (raw)
In-Reply-To: <20141022191336.70174815@uryu.home.lan>

I am aware of that. But it's a pain to do it. And then your local branch doesn't move forward when new stable releases come out. So I was suggesting we have a stable branch always available and known-good pointing to latest 1.X.X or 2.X.X release of latest stable 1.X or 2.X. It would also be friendly to maintenance programmers who want to submit patches to stable versions and encourage them to contribute stability fixes to DPDK just like Greg KH and the stable kernel guys do for the Long Term kernels.

Matthew.
-- 
Sent from my mobile device.

On October 22, 2014 6:43:36 AM PDT, Stephen Hemminger <stephen@networkplumber.org> wrote:
>On Wed, 22 Oct 2014 00:00:58 -0700
>Matthew Hall <mhall@mhcomputing.net> wrote:
>
>> What I think git in general and DPDK in particular are missing is,
>they have a 
>> tradition tags for releases, however I think this is broken because
>you can't 
>> easily append more stuff to tages.
>
>In git tags and branches are almost the same thing.
>You can easily create a local branch off of a tag.

  reply	other threads:[~2014-10-22 15:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21  8:22 Marc Sune
2014-10-21  8:36 ` Richardson, Bruce
2014-10-21  8:46   ` Thomas Monjalon
2014-10-21  9:14     ` Marc Sune
2014-10-21  9:28       ` Thomas Monjalon
2014-10-21  9:38         ` Marc Sune
2014-10-21 13:50           ` Neil Horman
2014-10-22  7:00         ` Matthew Hall
2014-10-22 13:43           ` Stephen Hemminger
2014-10-22 15:54             ` Matthew Hall [this message]
2014-10-21 13:01       ` Stephen Hemminger
2014-10-23  9:19         ` Marc Sune

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=F5F8A6AD-9A22-4C6B-AA47-3DC509685254@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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).