From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 71253 invoked by alias); 12 Mar 2017 01:48:45 -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 71199 invoked by uid 89); 12 Mar 2017 01:48:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=Branches, e2e9a61f5b29, Published, H*f:sk:B951D98 X-HELO: smtp.gentoo.org Received: from smtp.gentoo.org (HELO smtp.gentoo.org) (140.211.166.183) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 12 Mar 2017 01:48:21 +0000 Received: from vapier (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with SMTP id 3327F34106E; Sun, 12 Mar 2017 01:48:09 +0000 (UTC) Date: Sun, 12 Mar 2017 01:48:00 -0000 From: Mike Frysinger To: Petr Ovtchenkov Cc: Tristan Gingold , binutils@sourceware.org Subject: Re: version control policy Message-ID: <20170312014808.GH31094@vapier> Mail-Followup-To: Petr Ovtchenkov , Tristan Gingold , binutils@sourceware.org References: <20170308214155.58c71719@void-ptr.info> <20170310194946.11bfa75d@void-ptr.info> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4Epv4kl9IRBfg3rk" Content-Disposition: inline In-Reply-To: <20170310194946.11bfa75d@void-ptr.info> X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00162.txt.bz2 --4Epv4kl9IRBfg3rk Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1425 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? > >=20 > > Branches are created from master. >=20 > 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? > >=20 > > Published releases are created from branches. Usually, there is also a= tag on the commit for the > > release. >=20 > Well, gdb team set labels. Looks, that binutils team prefer branches inst= ead. 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 --4Epv4kl9IRBfg3rk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-length: 833 -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAljEqNgACgkQQWM7n+g3 9YFxZg/+N6a6TscKiEpe0Ye1IMPcbIxH4QvYzgnlIFjcnrAnVJw7PQLtTQYaX3Vt +r4eKj5razLs0U1rlEF2ozNXpsXDUA3gej6GNxA/6wm6cAuVmPQNutHRm3NVPN9k nFqpmHZe2//KqQ9sMslp+JQL/Ih9odIUWn63MKDyrBrF4TySavDiW2owZC7VHNc9 o2h6MT6KhOjsiDFFRCmmKxCGKQcjbIqnRTkpIFWeq9WwGF9ZUKlTxAQeKBXC25Pq kGyyfBA4hT+oc4MGdASzRbOwJtJ+PucFEN1AbQKRVYMuZmwYMaqTxghKhRBudnHh SP+LlY9u8wsVxkhwwGWs/9iRBaclMRB5GTMPIWegwa2szKXwMOgr8qfKaexlsMyo DqKI/079+OmzkOIOyBpKGvHFYAKVLQk9xA0nRgr8IHUzqUJ8O0fr5fMnXa3kJXUI EfjBNbm0GDeNKKXVwFvF0Jrq+3k8o7USxJnthe7sxb7j+flZAplLvYDY48X1cZ8Y +pPERVzYpEWfvf5KVmnF9Ua9svtbjBwGt7cfMdBnaP2aNG/izMuWeb9bu+lfIbs3 hrHRgLpWNUDt/HYgFhABOmnlRUtrzCHuLc+T+FKnbzYLgZSSyvcvlxbVk95209+O AJK0sSOXoAlUpJl+wfKe8OtaHoXd+lNwok5xGJOCTXhJZ7rDJs4= =zLmW -----END PGP SIGNATURE----- --4Epv4kl9IRBfg3rk--