From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Please don't use revision numbers on commit messages (and elsewhere). Date: Thu, 31 Mar 2011 23:36:07 +0200 Message-ID: References: <877hbfvwyo.fsf@wanadoo.es> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1301607404 4273 80.91.229.12 (31 Mar 2011 21:36:44 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 31 Mar 2011 21:36:44 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?UTF-8?Q?=C3=93scar_Fuentes?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 31 23:36:37 2011 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 1Q5PXg-000767-Dw for ged-emacs-devel@m.gmane.org; Thu, 31 Mar 2011 23:36:36 +0200 Original-Received: from localhost ([127.0.0.1]:48908 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q5PXf-0006rV-Vg for ged-emacs-devel@m.gmane.org; Thu, 31 Mar 2011 17:36:36 -0400 Original-Received: from [140.186.70.92] (port=53744 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q5PXa-0006rD-3I for emacs-devel@gnu.org; Thu, 31 Mar 2011 17:36:31 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q5PXY-0003SS-RG for emacs-devel@gnu.org; Thu, 31 Mar 2011 17:36:29 -0400 Original-Received: from mail-ew0-f41.google.com ([209.85.215.41]:45000) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q5PXY-0003SI-Ma for emacs-devel@gnu.org; Thu, 31 Mar 2011 17:36:28 -0400 Original-Received: by ewy9 with SMTP id 9so933605ewy.0 for ; Thu, 31 Mar 2011 14:36:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=fO5JovLSRWDaEzl3b+1FYBnx7xLnP5O0fHCoUN9ZpzQ=; b=c4ZFta2ihjOGUDE8gM3jdcLoFg1U7WMAilKc6trwToGl1rWqKTPAXusAR/A2bvb3D9 Vxynl812RiTvsL1sD66fcJG23LihkWXLNTCilfEcoWZS2MRAQN7KAHAD1lfLy046fOzU qsG9A856ZVGzs0Os5NJ9gqhoCw8K3hvscAmyA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=KT1OePB32RvefiC+r92kJj52MuDK+fxfTTNqZh3Y71AV9hxRfT0+NcPn6PveTPXiCV XnbY2O5ky2Xx0E6IbeKCNtM574PZwEPGIUMUWkcLt6Q2gPjFr2hV7+19IGCbO8b6BSF9 d8PWcEheV9Xg2NHvpt6dn+iyk4GwyXIXNp6LU= Original-Received: by 10.213.17.204 with SMTP id t12mr1042eba.102.1301607387111; Thu, 31 Mar 2011 14:36:27 -0700 (PDT) Original-Received: by 10.213.33.200 with HTTP; Thu, 31 Mar 2011 14:36:07 -0700 (PDT) In-Reply-To: <877hbfvwyo.fsf@wanadoo.es> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.215.41 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:137952 Archived-At: On Thu, Mar 31, 2011 at 10:47 PM, =C3=93scar Fuentes wrote= : > A revision number only makes sense on the branch where it was created > (and this only after setting some options, as Emacs did.) If I'm reading > the VC log on a random branch and see "Fix breakage introduced by rXXXX" > and want to look at the referenced revision, I need to switch to trunk > and hope that XXXX corresponds to one of its revisions. If a series of > commits on a feature branch mentions one another by revison number, > after merging them into trunk (or into any other branch) those numbers > are wrong. > > So, if you wish to refer to another revision on the commit message (or > anywhere else) please use the revision id, which is unique for every > commit. Why not both rev number and rev id?