From: Juanma Barranquero <lekktu@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Equivalent of release tags with bzr?
Date: Tue, 29 Dec 2009 22:46:42 +0100 [thread overview]
Message-ID: <f7ccd24b0912291346k4e7267ebu72e60488cf5787e7@mail.gmail.com> (raw)
In-Reply-To: <878wclfso7.fsf@stupidchicken.com>
> 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?
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=ARG
Branch in which to place the tag.
--usage Show usage message and options.
-r ARG, --revision=ARG
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 another
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
next prev parent reply other threads:[~2009-12-29 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 20:10 Equivalent of release tags with bzr? Chong Yidong
2009-12-29 20:43 ` Christian Faulhammer
2009-12-29 21:46 ` Juanma Barranquero [this message]
2009-12-29 21:59 ` Óscar Fuentes
2009-12-29 22:16 ` Giorgos Keramidas
2009-12-31 5:50 ` Ken Raeburn
2009-12-31 9:40 ` Andreas Schwab
2009-12-31 12:40 ` Christian Faulhammer
2009-12-31 13:51 ` Giorgos Keramidas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7ccd24b0912291346k4e7267ebu72e60488cf5787e7@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).