From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: Release tags Date: Wed, 05 Sep 2012 10:53:17 +0900 Message-ID: <877gs9teuq.fsf@uwakimon.sk.tsukuba.ac.jp> 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> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1346810013 3128 80.91.229.3 (5 Sep 2012 01:53:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 5 Sep 2012 01:53:33 +0000 (UTC) Cc: =?utf-8?Q?=C3=93scar?= Fuentes , emacs-devel@gnu.org To: Tim Cross Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 05 03:53:35 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 1T94oA-00061C-2T for ged-emacs-devel@m.gmane.org; Wed, 05 Sep 2012 03:53:34 +0200 Original-Received: from localhost ([::1]:53511 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T94o7-0007V2-17 for ged-emacs-devel@m.gmane.org; Tue, 04 Sep 2012 21:53:31 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:45607) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T94o4-0007Ux-C9 for emacs-devel@gnu.org; Tue, 04 Sep 2012 21:53:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T94o3-0002al-Ed for emacs-devel@gnu.org; Tue, 04 Sep 2012 21:53:28 -0400 Original-Received: from mgmt2.sk.tsukuba.ac.jp ([130.158.97.224]:43298) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T94o2-0002Zx-UJ for emacs-devel@gnu.org; Tue, 04 Sep 2012 21:53:27 -0400 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt2.sk.tsukuba.ac.jp (Postfix) with ESMTP id 9C612970885; Wed, 5 Sep 2012 10:53:17 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 5B7E31A3092; Wed, 5 Sep 2012 10:53:17 +0900 (JST) In-Reply-To: X-Mailer: VM 8.0.12-devo-585 under 21.5 (beta32) "habanero" b0d40183ac79 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 130.158.97.224 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:153027 Archived-At: Tim Cross writes: [Please trim irrelevant stuff you didn't write.] > I cannot see any emacs-24.2 tag in the main trunk. I suspect (but > don't know for sure) that this is because the tag was not made in the > emacs-24 branch before it was merged back into trunk. Right. What could and IMO should be done (ie, I do it when I'm RM :-) is to tag the branch point. That is the last "known good" point on the trunk (given the Emacs release process). > Obviously, I could just check out the emacs-24 branch. However, I was > hoping to avoid having to either switch branches Why? You're doing essentially the same thing anyway if you check out a tag. It's not a branch switch, but you've got the wrong code base for making changes to. ("Wrong" in the sense that you run a risk of unnecessary conflicts when merging your changes.) I'll grant that the bzr implementation of this gives me hives, but from the user point of view a shared repo (efficient storage of revisions common to the branches of interest) plus a lightweight checkout gives you the same effect as colocated branches for this purpose, at the slight cost of setting up a shared repo and learning an extra command IIRC. > An earlier post in this thread identifies the revision number where > the emacs-24.2 version was merged back into the dev trunk, so I can > achieve what I want using that revision number. No, you can't, if "known good revision" is what you want. Any instability introduced *in the trunk* since emacs-24.2 branched from the trunk is still in the trunk. You do not get a "known good" revision. You only get fixes to emacs-24.2 since the branch, but these should be pretty small, and won't address "new" instability. Steve