non-local tags and branches

[Thomas Arendsen Hein]

* Lluís Batlle <viriketo at gmail.com> [20060511 13:43]:
> I'm still trying to understand well the branching/tagging process in a
> repository... as far as I've understood, a repository 'tag' is done
> versioning a .hgtags file; isn't it? And therefore there is a commit for
> each repository tag. Is that commit done always from the tagged version, or
> from the actual parent?

Always from the current working directory's parent. If you want it
to be a direct child of the changeset you want to tag, just update
to that changeset. This will create a new head though which you
might want to merge, or just keep the head as the first changeset of
a newly created in-repo branch.

> According to which criteria are branches named (hg log -b) if there are no
> tags?

No names then, just changeset hashes.

> Another thing... the 'tip' always goes to the last commit. Imagine that
> someone puts a fix for a 0.6 version of Mercurial; then, a new developer
> clones the repository, and tries to start working for the latest code for
> the next release. How should he find, that he's working in a wrong branch?

hg heads (hg pull tells you if you just fetched a new head)

A solution for your confusion might be to use separate repositories
for separate branches, that's the original design of Mercurial.

Clones are cheap.

Thomas

-- 
Email: thomas at intevation.de
http://intevation.de/~thomas/