From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 114287 invoked by alias); 30 Dec 2016 06:18:43 -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 114263 invoked by uid 89); 30 Dec 2016 06:18:42 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy= X-HELO: einhorn.in-berlin.de Received: from einhorn.in-berlin.de (HELO einhorn.in-berlin.de) (192.109.42.8) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 30 Dec 2016 06:18:40 +0000 X-Envelope-From: doko@ubuntu.com Received: from [192.168.1.235] ([49.228.228.119]) (authenticated bits=0) by einhorn.in-berlin.de (8.14.4/8.14.4/Debian-8+deb8u1) with ESMTP id uBU6IRid030645 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 30 Dec 2016 07:18:30 +0100 Subject: Re: Binutils release 2.28 - soon To: Joel Brobecker References: <19E012B6-897D-476D-BD02-183EF834BC68@adacore.com> <5125B08E-62E4-4D26-A235-5D536FFD4929@adacore.com> <20161229044439.7dtw6cehsd7uohmu@adacore.com> <0b3c5056-ac30-1e8a-3edf-454072904165@ubuntu.com> <20161230054839.7mlqebjebj2kqyki@adacore.com> Cc: Tristan Gingold , binutils From: Matthias Klose Message-ID: <9e7726e4-9558-aed5-0bdb-9ab8da7d9fbc@ubuntu.com> Date: Fri, 30 Dec 2016 06:18:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161230054839.7mlqebjebj2kqyki@adacore.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-12/txt/msg00471.txt.bz2 On 30.12.2016 06:48, Joel Brobecker wrote: >> thanks! I still think using the date is more expressive than using a >> commit ID. So what about only bumping the date if the last commit is >> not a date bump? > > In my opinion, git describe is much much more precise than a date. > Eg: > > % git describe > ref-tag-190-gdda5790 > > From there, I know that the commit is 190 commits past a tag called > ref-tag. This only seems to work when there is a tag once the release branch is created.