.hgtags not cloned

[Peter Arrenbrecht]

I believe this is the current design. The first "hg tag" creates and
commits the .hgtags file. But it records as rel_1.0 the revision just
_prior_ to the commit of .hgtags. So the clone at that revision does
not get the .hgtags. Or, if .hgtags already existed, it does not get
the entry with the cloned tag. Unexpected, but that's how it is, I
think.
-peo

On 10/16/07, Sebastian Hauer <sebastian.hauer at gmail.com> wrote:
> Hi,
> I just noticed that .hgtags does not necessarily get cloned when I do
> the following:
>
> 1. Tag the project (this is the first tag in my case)
>     hg tag rel_1.0
>     (As expected .hgtags gets created and contains the tag now)
>
> 2. Clone the repo based on the release tag:
>     cd ..
>     hg clone -r rel_1.0 MyProject MyProject-rel1
>     (MyProject-rel1 does not contain the .hgtags file from the MyProject repo)
>
> Is this a know bug or am I using it wrong?
>
> Regards,
> Sebastian
>
> PS: Tested on Windows with mercurial 0.9.4
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>