From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f176.google.com (mail-pd0-f176.google.com [209.85.192.176]) by dpdk.org (Postfix) with ESMTP id 9C0237E75 for ; Thu, 23 Oct 2014 02:37:56 +0200 (CEST) Received: by mail-pd0-f176.google.com with SMTP id fp1so902pdb.21 for ; Wed, 22 Oct 2014 17:46:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=Z3ralG5fFYArvz+jQcO6iX2bg/UUmQ1uh7AyAbuzFe4=; b=PqFfoYKTvSFoEOHS2IciBd1iVMsEFitr2yCHk4MDbMvoSBaVCI77JvdTKOyAaS3WLq O0MBeK32mwAHjiDUw8q/g54na2oNKSuhYk9LdamOgoCLAJHgngQm61hN8f3zxZyo9WaD t8xq1FmmNl5GZRaHuY5D1HKJFddsYx71rGQU6na6usKl4sy/opaLtAd2TR3rNW8H5cUU 65xVfZb306Vbf4JIALwqXD7y0uu3B7JFXaVmVF6kn8DHzCzpzUZtfticDsKc7dEm2KMk 7NvaxgLK2aOm03shW35Mmm+D2HgrqS3d1Kcy9PoRSr45N/5OAbcNv8vzYjhhyGQuyhfL 1K7w== X-Gm-Message-State: ALoCoQmInNjJeBgg5APto32IjThi/lsZOuSDJuV6C4zZUtcwUb8+9QzPWow8C8/rKnRoZmVzPHal X-Received: by 10.68.87.37 with SMTP id u5mr1479935pbz.128.1414025178135; Wed, 22 Oct 2014 17:46:18 -0700 (PDT) Received: from uryu.home.lan ([14.141.84.68]) by mx.google.com with ESMTPSA id df1sm205120pbb.2.2014.10.22.17.46.16 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 22 Oct 2014 17:46:17 -0700 (PDT) Date: Tue, 21 Oct 2014 18:31:58 +0530 From: Stephen Hemminger To: Marc Sune Message-ID: <20141021183158.0dbd5c0e@uryu.home.lan> In-Reply-To: <54462403.3060107@bisdn.de> References: <544617E0.80502@bisdn.de> <59AF69C657FD0841A61C55336867B5B0344210F9@IRSMSX103.ger.corp.intel.com> <39275062.2hPoVIfNVy@xps13> <54462403.3060107@bisdn.de> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org Subject: Re: [dpdk-dev] development/integration branch? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Oct 2014 00:37:57 -0000 On Tue, 21 Oct 2014 11:14:43 +0200 Marc Sune 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.