From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Teemu Likonen Newsgroups: gmane.emacs.devel Subject: Re: `about-emacs' - what about the revno? Date: Sun, 29 Aug 2010 07:56:25 +0300 Message-ID: <874oeec8zq.fsf@mithlond.arda> References: <83occmlogo.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1283057812 14575 80.91.229.12 (29 Aug 2010 04:56:52 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 29 Aug 2010 04:56:52 +0000 (UTC) Cc: Drew Adams , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Aug 29 06:56:51 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OpZwo-0001cD-RZ for ged-emacs-devel@m.gmane.org; Sun, 29 Aug 2010 06:56:51 +0200 Original-Received: from localhost ([127.0.0.1]:54469 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OpZwo-0003M4-8K for ged-emacs-devel@m.gmane.org; Sun, 29 Aug 2010 00:56:50 -0400 Original-Received: from [140.186.70.92] (port=53883 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OpZwh-0003L9-7q for emacs-devel@gnu.org; Sun, 29 Aug 2010 00:56:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OpZwf-0000lV-Sr for emacs-devel@gnu.org; Sun, 29 Aug 2010 00:56:43 -0400 Original-Received: from mta-out.inet.fi ([195.156.147.13]:45847 helo=kirsi2.inet.fi) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OpZwe-0000ko-7b; Sun, 29 Aug 2010 00:56:40 -0400 Original-Received: from mithlond.arda (84.251.132.215) by kirsi2.inet.fi (8.5.122) id 4C33307D01C24CE0; Sun, 29 Aug 2010 07:56:28 +0300 Original-Received: from dtw by mithlond.arda with local (Exim 4.69) (envelope-from ) id 1OpZwP-00017M-Eb; Sun, 29 Aug 2010 07:56:25 +0300 In-Reply-To: <83occmlogo.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 28 Aug 2010 18:57:27 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:129378 Archived-At: * 2010-08-28 18:57 (+0300), Eli Zaretskii wrote: > "Drew Adams" wrote: >> If the "revno" is important info for identifying an Emacs build, then >> perhaps we should include it in such user-facing info. If not, then >> perhaps developers could refer in some other way (by date?) to the >> code that contains a given fix. > > This has come up before, but the discussion was inconclusive (IIRC) > because of 2 reasons: > > . revno is not unique: two different branches can have the same > revno for two very different code bases > > . revision-id, an alternative method of specifying a revision, _is_ > unique, but it's long and a mouthful: > > eliz@gnu.org-20100828152310-v42vqrt01k788siu Another reason to use Git instead. With "git describe" you get unique commit identifiers which are also human-readable and have an increasing commit counter in it, for example: v23.2-54-g1234ab It consists of the latest tag name (e.g., "v23.2") which is reachable from the current commit, the commit count (54) after the tag and an abbreviated SHA1 ID of the current commit (1234ab). Some projects that use Git include such a version string automatically to program's build. Git commands understand the string as a version identifier. When executing "git describe" on a tagged commit it outputs just the tag name (e.g., "v23.2") so it automatically gives the right answer for releases too (can be useful when creating release tarballs). Sorry for pushing Git again but it's just better. > In general, a bugfix should appear in the ChangeLog files with the bug > number, so you should be able to track bugfxes that way. More elegant way is to write something like "Closes: bug#1234" in the appropriate commit message and have the central Emacs repository use a post-receive hook script that will detect the keyword in commit messages. The hook script could then send control message to the bug tracker and close the bug with a message like this: This issue has been fixed by the commit Commit: v23.2-57-gab1cd2 Author: Dave Developer Date: 2010-00-00 00:00:00 +0000 You can use command "git show v23.2-57-gab1cd2" in the Emacs Git repository to see the details.