DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Marc Sune <marc.sune@bisdn.de>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] development/integration branch?
Date: Tue, 21 Oct 2014 18:31:58 +0530	[thread overview]
Message-ID: <20141021183158.0dbd5c0e@uryu.home.lan> (raw)
In-Reply-To: <54462403.3060107@bisdn.de>

On Tue, 21 Oct 2014 11:14:43 +0200
Marc Sune <marc.sune@bisdn.de> wrote:

> On 21/10/14 10:46, Thomas Monjalon wrote:
> > My balance is different because I have a simpler solution for Marc's problem:
> > 	git fetch && git merge $(git tag | grep -v -- -rc | tail -n1)
> Thomas,
> We all know we _can_ do this. But is it really necessary? We should be 
> all as lazy as possible and make it easy for users IMHO. `git pull` is 
> easier :)
> I don't see any drawback of using a development branch, except if you 
> consider the extra push to master per release a drawback.
> Also think about new users downloading the repo for the first time. They 
> are forced to do this right now if they want to checkout the latest stable.
> marc

For most project master is the development branch and where patches
should be targeted.

If you want stable branch, then either use releases or volunteer to
maintain a "master-stable" branch.

  parent reply	other threads:[~2014-10-23  0:37 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
2014-10-21 13:01       ` Stephen Hemminger [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141021183158.0dbd5c0e@uryu.home.lan \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=marc.sune@bisdn.de \


* 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).