From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Release tags Date: Wed, 05 Sep 2012 05:49:24 +0200 Message-ID: <87zk55jfi3.fsf@wanadoo.es> References: <04A8931A-A044-4F8A-86FD-7AA70DA2B5E3@mit.edu> <87d32awhc7.fsf@gnu.org> <87wr0aldw0.fsf@gmail.com> <83pq62ec1i.fsf@gnu.org> <87fw6x505b.fsf@gnu.org> <87mx15lr1k.fsf@wanadoo.es> <87y5kpydsr.fsf@gnu.org> <87ipbtlk7v.fsf@wanadoo.es> <874nndkxj2.fsf@wanadoo.es> <87392xtbei.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1346816979 17602 80.91.229.3 (5 Sep 2012 03:49:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 5 Sep 2012 03:49:39 +0000 (UTC) Cc: Tim Cross , emacs-devel@gnu.org To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 05 05:49:40 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1T96cR-0000vb-7j for ged-emacs-devel@m.gmane.org; Wed, 05 Sep 2012 05:49:35 +0200 Original-Received: from localhost ([::1]:43924 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T96cO-0000Ts-FB for ged-emacs-devel@m.gmane.org; Tue, 04 Sep 2012 23:49:32 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:35210) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T96cM-0000Tn-Gd for emacs-devel@gnu.org; Tue, 04 Sep 2012 23:49:31 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T96cL-0006EB-E0 for emacs-devel@gnu.org; Tue, 04 Sep 2012 23:49:30 -0400 Original-Received: from impaqm3.telefonica.net ([213.4.138.19]:38990 helo=telefonica.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T96cL-0006Dy-3w for emacs-devel@gnu.org; Tue, 04 Sep 2012 23:49:29 -0400 Original-Received: from IMPmailhost5.adm.correo ([10.20.102.126]) by IMPaqm3.telefonica.net with bizsmtp id vF3h1j0122jdgqJ3PFpS5x; Wed, 05 Sep 2012 05:49:26 +0200 Original-Received: from qcore ([79.147.14.108]) by IMPmailhost5.adm.correo with BIZ IMP id vFpQ1j00A2Kt1p31lFpR2S; Wed, 05 Sep 2012 05:49:26 +0200 X-Brightmail-Tracker: AAAAAA== X-original-sender: 981711563@telefonica.net In-Reply-To: <87392xtbei.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Wed, 05 Sep 2012 12:07:49 +0900") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 213.4.138.19 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:153031 Archived-At: "Stephen J. Turnbull" writes: > =C3=93scar Fuentes writes: > > > If you know the revision that corresponds to the emacs-24.2 tag > > upstream, why don't you tag your private branch yourself? > > Because he doesn't have that revision to tag. If he did, he'd have > the tag, too. No, he says that he has an up-to-date checkout of `trunk', which necessarily contains the revision tagged as `emacs-24.2', because it was merged into `trunk' almost 2 weeks ago. He also mentions that he knows the revision number of the merge. His problem is that the tag (not the revision) is missing from his private repo. > So he would need to branch emacs-24.2, and he doesn't > want to do that (I'm not sure why, so I asked, we'll see what he > says). Dealing with multiple branches on bzr is a bit of an inconvenience, for several reasons. One of them is mentioned by the OP: you end having multiple working copies around, or having to learn and remember tricks for reusing the same working copy. As the OP plans to use the emacs-24.2 stable point only in the rare cases when `trunk' is in a unusable state, his reluctance is understandable.