[PATCH] add smart-tags option to hg identify

[Matt Mackall]

On Sun, 2009-07-26 at 21:04 +0200, Ronny Pfannschmidt wrote:
> On Sun, 2009-07-26 at 13:42 -0500, Matt Mackall wrote:
> > On Sun, 2009-07-26 at 12:05 +0200, Ronny Pfannschmidt wrote:
> > > # HG changeset patch
> > > # User Ronny Pfannschmidt <Ronny.Pfannschmidt at gmx.de>
> > > # Date 1248602733 -7200
> > > # Node ID 58802fdc974527632219ef0adb2c58668f3b0f4e
> > > # Parent  ca143d86727cdf7cfc079b6fc9a1eb09eed2dc72
> > > add smart-tags option to hg identify
> > 
> > No thanks. The tagged changeset and the tagging changeset are different
> > csets. Making id intentionally confuse them and calling that 'smart'
> > doesn't improve matters.
> > 
> Yes, its not that smart and could use a different name and maybe a
> prefix.
> 
> However the fact that a Tags creates a new revision is a pain for me and
> requires more steps i shouldn't forget in the release process.
> 
> I don't want to have to care about having to update to a specific tagged
> version again to get the propper id (after all hg is the only dvcs where
> i have to deal with that).
> 
> All i want have to do for a release is
> 1. make a tag
> 2. invoke a simple script

Why don't you reduce that to:

1. invoke a simple script that also makes a tag

And that script can simply be:

hg tag $1
hg co $1
# do the rest of my build
hg up


My Mercurial release script actually goes a step further:

VER=$1
rm -rf release-build-$1
hg clone -q . release-build-$1 || exit 0
cd release-build-$1
hg tag $1
hg sign -k mpm $1 || exit 0
hg co $1
...

If for some reason, something goes wrong with the release script, I can
just nuke the build directory.

-- 
http://selenic.com : development and support for Mercurial and Linux