From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas.monjalon@6wind.com> Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by dpdk.org (Postfix) with ESMTP id 7518A7E7A for <dev@dpdk.org>; Tue, 21 Oct 2014 11:20:49 +0200 (CEST) Received: by mail-wi0-f171.google.com with SMTP id em10so9434944wid.16 for <dev@dpdk.org>; Tue, 21 Oct 2014 02:29:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=CbKsiV+6LNPmoBoihBC3LYqepUqgVUeRctlcauIT+RE=; b=KIypVLYv2o8n6TRLq0mWu5ihp5YJh6gGMjIgLpbwNTGUb3cruS6NT7Nt/OlXR0QYTB zBSf/YUY2bFikncFjO4xYf0Q2l5XKEpasmfY6zqC7MXGOGzqVIUm24ItpAI4BTIcHM6I TmNoVSxi+3WeUdJValsZV0NsG3+8jCoZbx4EbPhUGlqBd7mUzoyGzbFQSiw/r0uveUTF PioPyiCxFYGIpZaqhK/uBXtGlM9l/R4/Kg8HXgvr9RstgR+ApCaEuWbcuaSDkoMJ2xQ2 myjFMGfKLU3Ro9V4OjTWkfzttOayLNNH5zW7yleE9MabrXWUfcHNJlRFfnyzUFhwQ7aW fI/A== X-Gm-Message-State: ALoCoQmvTy1ba5E2Hn/UzQG/ft8kCcxOOpko7MIC3i9B2BHd+w7aeRJTBMwU2iV9yQ2JXu2PHHBp X-Received: by 10.194.78.238 with SMTP id e14mr18401756wjx.106.1413883744087; Tue, 21 Oct 2014 02:29:04 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id dg3sm10739828wib.14.2014.10.21.02.29.02 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Oct 2014 02:29:03 -0700 (PDT) From: Thomas Monjalon <thomas.monjalon@6wind.com> To: Marc Sune <marc.sune@bisdn.de> Date: Tue, 21 Oct 2014 11:28:47 +0200 Message-ID: <3074245.k7N1CrtUjD@xps13> Organization: 6WIND User-Agent: KMail/4.14.1 (Linux/3.16.4-1-ARCH; KDE/4.14.1; x86_64; ; ) In-Reply-To: <54462403.3060107@bisdn.de> References: <544617E0.80502@bisdn.de> <39275062.2hPoVIfNVy@xps13> <54462403.3060107@bisdn.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Tue, 21 Oct 2014 09:20:49 -0000 2014-10-21 11:14, Marc Sune: > 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) > > 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 :) Yes and lazy users download tarballs. > I don't see any drawback of using a development branch, except if you > consider the extra push to master per release a drawback. No I don't care to push one more thing. But I care about the message brought by such change. It would mean that we can break the development branch and that most of developers don't test it nor base their patches on the latest commit. It's all about simple rules and messages. > 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. New users will get the latest release and expect to see current work in progress right after cloning the git tree (in master branch). It's also more common to see work in progress in default branch in cgit. -- Thomas