From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Equivalent of release tags with bzr?
Date: Tue, 29 Dec 2009 22:59:52 +0100 [thread overview]
Message-ID: <87aax1o2zr.fsf@telefonica.net> (raw)
In-Reply-To: 878wclfso7.fsf@stupidchicken.com
Chong Yidong <cyd@stupidchicken.com> writes:
> 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?
As Juanma says, there is a `tag' command. Sadly, it seems
underdocumented.
I did some experiments and it seems to work this way:
on your local trunk mirror,
bzr tag <name>
will tag the current tip revision with <name>. If your local mirror is a
bound branch or checkout (the recommended setup on our bzr guides for
emacs devs) it will automatically send the tag upstream. If you are
tagging on a proper branch, you'll need a `push' for propagating it; the
push command will report that it is nothing to push, but it is a lie: it
actually pushed the tag to its push location.
Later, you can operate with the tagged revision with the syntax
tag:<name>, so for instance
bzr log -r tag:<name>..
will show the log from the tagged revision to now.
bzr branch -r tag:<name> URL
will create a branch with the tagged revision as its tip.
You can see a list of availabe tags on the current branch with
bzr tags
HTH
--
Óscar
next prev parent reply other threads:[~2009-12-29 21:59 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
2009-12-29 21:59 ` Óscar Fuentes [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aax1o2zr.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.