From: Andy Moreton <andrewjmoreton@gmail.com>
To: 22083@debbugs.gnu.org
Subject: bug#22083: 25.0.50; hg: adding tag enhances the rev, modeline does not reflect
Date: Mon, 07 Dec 2015 14:36:11 +0000 [thread overview]
Message-ID: <868u56qqas.fsf@gmail.com> (raw)
In-Reply-To: <87h9jzy70u.fsf@mat.ucm.es>
On Sat 05 Dec 2015, Dmitry Gutov wrote:
> On 12/05/2015 02:24 PM, Andy Moreton wrote:
>
>> That is normal - mercurial stores tags in a plain text file .hgtags at
>> the root of the repo, which is versioned the same way as any other file.
>>
>> This means that adding a tag is effectively the same as editing
>> .hgtags and committing the change.
>
> Does that mean that the set of available tags is dependent on the current
> branch? And you can't simply check out a tag, you also have to know which
> branch it is on?
You don't need to know which branch a tag is on, you can simply checkout
a tag as expected. You do needs to ensure that the .hgtags file is
handled properly when merging branches.
The Mercurial book is a little old, but has some useful detail:
http://hgbook.red-bean.com/read/managing-releases-and-branchy-development.html
AndyM
next prev parent reply other threads:[~2015-12-07 14:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 13:51 bug#22083: 25.0.50; hg: adding tag enhances the rev, modeline does not reflect Uwe Brauer
2015-12-04 3:09 ` Dmitry Gutov
2015-12-04 8:55 ` Eli Zaretskii
2015-12-04 11:41 ` Dmitry Gutov
2015-12-04 14:27 ` Eli Zaretskii
2015-12-04 14:43 ` Dmitry Gutov
2015-12-04 14:51 ` Eli Zaretskii
2015-12-04 15:15 ` Dmitry Gutov
2015-12-04 15:19 ` Eli Zaretskii
2015-12-04 15:21 ` Dmitry Gutov
2015-12-04 15:37 ` Eli Zaretskii
2015-12-04 15:46 ` Dmitry Gutov
2015-12-04 16:13 ` Eli Zaretskii
2015-12-04 17:54 ` Dmitry Gutov
2015-12-04 18:27 ` Eli Zaretskii
2015-12-04 12:02 ` Uwe Brauer
2015-12-05 6:08 ` Dmitry Gutov
2015-12-05 12:24 ` Andy Moreton
2015-12-05 19:01 ` Uwe Brauer
2015-12-05 19:08 ` Dmitry Gutov
2015-12-07 14:36 ` Andy Moreton [this message]
2015-12-07 22:05 ` Dmitry Gutov
2015-12-05 19:11 ` Uwe Brauer
2015-12-05 19:55 ` Dmitry Gutov
2015-12-05 21:36 ` Uwe Brauer
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=868u56qqas.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=22083@debbugs.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.