From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19381 invoked by alias); 13 Mar 2017 05:41:05 -0000 Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org Received: (qmail 19240 invoked by uid 89); 13 Mar 2017 05:40:59 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.3 required=5.0 tests=AWL,BAYES_00,KAM_INFOUSMEBIZ,KAM_LAZY_DOMAIN_SECURITY,RDNS_DYNAMIC autolearn=no version=3.3.2 spammy=H*M:info, sheer, talent, H*MI:sk:B951D98 X-HELO: void-ptr.info Received: from pppoe.185.44.68.223.lanport.ru (HELO void-ptr.info) (185.44.68.223) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 13 Mar 2017 05:40:57 +0000 Received: from ptr by void-ptr.info with local (Exim 4.72) (envelope-from ) id 1cnIiy-0004M2-9o; Mon, 13 Mar 2017 08:40:52 +0300 Date: Mon, 13 Mar 2017 05:41:00 -0000 From: Petr Ovtchenkov To: Mike Frysinger Cc: Tristan Gingold , binutils@sourceware.org Subject: Re: version control policy Message-ID: <20170313084052.57584a1c@void-ptr.info> In-Reply-To: <20170312014808.GH31094@vapier> References: <20170308214155.58c71719@void-ptr.info> <20170310194946.11bfa75d@void-ptr.info> <20170312014808.GH31094@vapier> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00174.txt.bz2 On Sat, 11 Mar 2017 20:48:08 -0500 Mike Frysinger wrote: > On 10 Mar 2017 19:49, Petr Ovtchenkov wrote: > > On Fri, 10 Mar 2017 15:15:05 +0100 Tristan Gingold wrote: > > > > On 08 Mar 2017, at 19:41, Petr Ovtchenkov wrote: > > > > - What the principles of branches? I.e. what the relation between, > > > > say, master, and gdb-7.12-branch? > > > > > > Branches are created from master. > > > > Do you really see on commits graph? > > sorry, but what does this mean ? > > > Because binutils and gdb share repo and build infrastructure, > > but has no clean code exchange between gdb/binutils branches, > > what gdb will build when I make build from, say, e2e9a61f5b29 ? > > both projects share the master branch, and it's up to each project > to choose when to branch based on their own release schedule. > > giving a random commit doesn't make much sense in the git world. > what branch are you looking at ? > > > > > What the relation between binutils-2_28-branch and published > > > > binutils 2.28, gdb-7.12-branch and published GDB 7.12.1? > > > > > > Published releases are created from branches. Usually, there is also a tag on the commit for > > > the release. > > > > Well, gdb team set labels. Looks, that binutils team prefer branches instead. > > there's no such thing as "labels" in git. Tristan is correct: > both projects create release branches, and then they tag their > releases from those branches when they're ready. > > > And both teams push to master on daily development basis, right? > > correct > -mike Hmm, you have sheer talent to give trivial answers and just cut off some (inconvenient?) questions. Let's repeat: Is bot's commits (like 40d57b1947) really useful? I see problems from ones, but not understand benefit. Can you explain advantage of bot's commits that outweigh garbage in the commit tree? The second question was (release numbers are mentioned below as example only): I want to build binutils 2.28 _and_ gdb 7.12.1 from primary git repo. What branch(s), tag(s), ... I should use? If commits points of gdb release and binutils release are different, what I should say to build - binutils without gdb (i.e. --disable-gdb --disable-libdecnumber --disable-readline --disable-sim) - gdb without binutils (?) The solution of this problem isn't clear for me, becouse I'm unsure that one installation will not partially overwrite another. Thanks, -- - ptr