From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: Equivalent of release tags with bzr? Date: Tue, 29 Dec 2009 22:46:42 +0100 Message-ID: References: <878wclfso7.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1262123241 6347 80.91.229.12 (29 Dec 2009 21:47:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 29 Dec 2009 21:47:21 +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 22:47:14 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 1NPjuL-00066x-3F for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2009 22:47:13 +0100 Original-Received: from localhost ([127.0.0.1]:45618 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPjuL-0007vH-FW for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2009 16:47:13 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NPjuH-0007ur-3b for emacs-devel@gnu.org; Tue, 29 Dec 2009 16:47:09 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NPjuB-0007tF-VN for emacs-devel@gnu.org; Tue, 29 Dec 2009 16:47:08 -0500 Original-Received: from [199.232.76.173] (port=44738 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPjuB-0007tA-QG for emacs-devel@gnu.org; Tue, 29 Dec 2009 16:47:03 -0500 Original-Received: from mail-bw0-f215.google.com ([209.85.218.215]:52483) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NPjuB-0004Hs-Gh for emacs-devel@gnu.org; Tue, 29 Dec 2009 16:47:03 -0500 Original-Received: by bwz7 with SMTP id 7so8007305bwz.26 for ; Tue, 29 Dec 2009 13:47:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=utoocVwzUEqnW8wny/ig63jsFDdjbw8Bvxp/hMXqLD0=; b=CVl2Tm4tm5GlL175W21ogxpA+DSXSVpfZr9+Uf8pMVmE79j9CAvtxwZXqayRVStCow 4kUMm9RIguqs5QKv3R+DgVyZRwrLW9zwYrCII5C2YriP8MYzHzKDPch63VRb8kA4oV9P R64NofP/lliXZPdnNbwbD0SsQMd97QrXRKLWw= 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=qgJXdrCMcOxsHdIXPNoVweTRc0aOM83LUn1EpIvggPu7Ro52IDp9bAijEgm0iMS4Hi 5aETDu03abM/1A8lMyPWYmUT+4uvvsP50LmxjbdM9RdhYkDYvkqFoP3OLCikDGmjyky8 3xADE/MSUEbgmT9AS8ZTXE+i1J7mHol7yx60I= Original-Received: by 10.204.152.27 with SMTP id e27mr5995910bkw.192.1262123222151; Tue, 29 Dec 2009 13:47:02 -0800 (PST) In-Reply-To: <878wclfso7.fsf@stupidchicken.com> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:118991 Archived-At: > With CVS, I would tag each pretest with a cvs tag, with > `cvs tag EMACS_PRETEST_XX_YY_ZZ'. =C2=A0Now that we have moved to Bzr, wh= at > should be the corresponding procedure? There's a "bzr tag" command. Isn't that what you're looking for? Purpose: Create, remove or modify a tag naming a revision. Usage: bzr tag TAG_NAME Options: --force Replace existing tags. -v, --verbose Display more information. -h, --help Show help message. -q, --quiet Only display errors and warnings. -d ARG, --directory=3DARG Branch in which to place the tag. --usage Show usage message and options. -r ARG, --revision=3DARG See "help revisionspec" for details. --delete Delete this tag rather than placing it. Description: Tags give human-meaningful names to revisions. Commands that take a -r (--revision) option can be given -rtag:X, where X is any previously created tag. Tags are stored in the branch. Tags are copied from one branch to anothe= r along when you branch, push, pull or merge. It is an error to give a tag name that already exists unless you pass --force, in which case the tag is moved to point to the new revision. To rename a tag (change the name but keep it on the same revsion), run ``= bzr tag new-name -r tag:old-name`` and then ``bzr tag --delete oldname``. See also: commit, tags Juanma