[PATCH 1 of 1 RFC] tag: abort if not at a branch head

Tatham Oddie tatham at oddie.com.au
Thu Dec 9 05:52:05 CST 2010


Hi,

> I'm hard-pressed to think of any realistic use cases for committing a tag
at somewhere other than a branch head. Can anyone think of one?

For the code behind pdfink.com, our repo looks like this:

C:\Code\PdfInk>hg tags
tip                              201:4d62608def72
live-app                         186:5dc8be44ed72
v1.0.0.19                        186:5dc8be44ed72
v1.0.0.18                        178:67b0811eb417
v1.0.0.17                        161:ee710708b668
live-site                        159:e8d360e86aae
v1.0.0.16                        131:8674fbe54c2b
v1.0.0.15                        114:324c4a62f6fb
v1.0.0.14                        112:56ba448b8635
v1.0.0.13                        103:589a93eb802d
v1.0.0.12                         90:7ee72b2aea5d
v1.0.0.11                         73:4079ca5d1e32
v1.0.0.10                         58:7a46f751a990
v1.0.0.9                          36:0339162de312
v1.0.0.8                          32:a0e0aec4203a

Each version gets tagged when we cut it, but then we also have two tags that
mark whatever is the currently published app + site.

Use case #1: Because tagging the version results in a commit, we have to
"back tag" for when we apply live-app.

In our case, the process of tagging it as live-app or live-site actually
triggers an automated build that publishes it all the way through to
production. That is, we are saying "make this the live version" as opposed
to "this is the live version".

Use case #2: If we wanted to roll back the site quickly, we could just move
the live-site tag.

Maybe we're abusing tags ... but that's what we currently do.


--
Tatham Oddie
au mob: +61 414 275 989, us cell: +1 213 280 9140, skype: tathamoddie
If you're printing this email, you're doing it wrong. This is a computer,
not a typewriter.


-----Original Message-----
From: mercurial-devel-bounces at selenic.com
[mailto:mercurial-devel-bounces at selenic.com] On Behalf Of Matt Mackall
Sent: Tuesday, 7 December 2010 11:14 AM
To: Kevin Bullock
Cc: mercurial-devel at selenic.com
Subject: Re: [PATCH 1 of 1 RFC] tag: abort if not at a branch head

On Mon, 2010-12-06 at 13:56 -0600, Kevin Bullock wrote:
> # HG changeset patch
> # User Kevin Bullock <kbullock at ringworld.org> # Date 1291665075 21600 
> # Node ID f52e752c6d5f90352bb29ba6c2543656f6e4531e
> # Parent  8c6b7a5f38c4585b1b2c2ceaffa8023f36a18479
> tag: abort if not at a branch head
> 
> Since it's usually only desirable to make tag commits on top of branch 
> heads, abort if the working dir parent is not a branch head. 
> -f/--force may be passed to commit at a non-head anyway.

I'm hard-pressed to think of any realistic use cases for committing a tag at
somewhere other than a branch head. Can anyone think of one?

--
Mathematics is the supreme nostalgia of our time.


_______________________________________________
Mercurial-devel mailing list
Mercurial-devel at selenic.com
http://selenic.com/mailman/listinfo/mercurial-devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6398 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20101209/2f4f624c/attachment.bin>


More information about the Mercurial-devel mailing list