From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Giorgos Keramidas Newsgroups: gmane.emacs.devel Subject: Re: Equivalent of release tags with bzr? Date: Wed, 30 Dec 2009 00:16:18 +0200 Message-ID: <87r5qdxw7h.fsf@kobe.laptop> References: <878wclfso7.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1262125004 11680 80.91.229.12 (29 Dec 2009 22:16:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 29 Dec 2009 22:16:44 +0000 (UTC) Cc: emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 29 23:16:36 2009 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.50) id 1NPkMk-0002n9-8w for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2009 23:16:34 +0100 Original-Received: from localhost ([127.0.0.1]:44673 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPkMk-0005jK-JI for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2009 17:16:34 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NPkMf-0005jF-Ln for emacs-devel@gnu.org; Tue, 29 Dec 2009 17:16:29 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NPkMb-0005if-1z for emacs-devel@gnu.org; Tue, 29 Dec 2009 17:16:29 -0500 Original-Received: from [199.232.76.173] (port=50728 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPkMa-0005ic-SZ for emacs-devel@gnu.org; Tue, 29 Dec 2009 17:16:24 -0500 Original-Received: from poseidon.ceid.upatras.gr ([150.140.141.169]:57917) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NPkMa-00087x-HS for emacs-devel@gnu.org; Tue, 29 Dec 2009 17:16:24 -0500 Original-Received: from mail.ceid.upatras.gr (unknown [10.1.0.143]) by poseidon.ceid.upatras.gr (Postfix) with ESMTP id 54C00EB4766; Wed, 30 Dec 2009 00:16:23 +0200 (EET) Original-Received: from localhost (europa.ceid.upatras.gr [127.0.0.1]) by mail.ceid.upatras.gr (Postfix) with ESMTP id BB98344FE4; Wed, 30 Dec 2009 00:16:25 +0200 (EET) X-Virus-Scanned: amavisd-new at ceid.upatras.gr Original-Received: from mail.ceid.upatras.gr ([127.0.0.1]) by localhost (europa.ceid.upatras.gr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id agHi2zft7Q-d; Wed, 30 Dec 2009 00:16:25 +0200 (EET) Original-Received: from kobe.laptop (ppp-94-64-219-207.home.otenet.gr [94.64.219.207]) by mail.ceid.upatras.gr (Postfix) with ESMTP id 6B84144FE2; Wed, 30 Dec 2009 00:16:25 +0200 (EET) Original-Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.3/8.14.3) with ESMTP id nBTMGLCv002366 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Dec 2009 00:16:21 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Original-Received: (from keramida@localhost) by kobe.laptop (8.14.3/8.14.3/Submit) id nBTMGKgf002355; Wed, 30 Dec 2009 00:16:20 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) In-Reply-To: <878wclfso7.fsf@stupidchicken.com> (Chong Yidong's message of "Tue, 29 Dec 2009 15:10:00 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.90 (berkeley-unix) X-detected-operating-system: by monty-python.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:118993 Archived-At: On Tue, 29 Dec 2009 15:10:00 -0500, Chong Yidong wrote: > With CVS, I would tag each pretest with a cvs tag, with > `cvs tag EMACS_PRETEST_XX_YY_ZZ'. Now that we have moved to Bzr, what > should be the corresponding procedure? You can just run "bzr tag EMACS_PRETEST_XX_YY_ZZ". This will not show up as a commit in the history, but the new tags will be visible in the output of "bzr tags". If the branch you tagged is a _bound_ branch, the tag will be sent to the remote branch too. If your local branch is not bound, then you can "bzr push" it. You can ignore the slightly misleading message "bzr push" will show. For some reason bzr treats tags in a special way reports that "no revisions have been pushed", but the tag is installed in the remote repository as one would expect.