Feature request: local branches
Daniel Holth
dholth at fastmail.fm
Thu Feb 1 05:23:41 UTC 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
One of my concerns with hg's named branches is that I am more
comfortable with prolific branch naming if I don't have to share the
names in history. Sure, I can transplant it later, but what if
Mercurial just allowed us to store local branches in the .hg/ directory?
How It Works:
A file .hg/localbranches contains lines "changesetid true name" or
"changesetid false name"
The changesetid is of the first revision that is part of the branch.
All children of that revision are also part of the branch, and the
branch ends in the normal way (update to another branch; hg merge branch).
The boolean tells us whether the branch is public or private. If the
branch is private, then "hg pull" does not pull that branch by
default. A developer might want to arrange that all his branches are
private except for an outgoing branch. By default you are still
allowed to pull any branch by mentioning its name. Either way, the
local branch names are not propagated in any way by the pull.
End feature.
When I'm working with branches in a single repository, I often want to
find the first merge changeset in the ancestry of a particular
changeset ("hg base -r revision"?) I also often want to log but
restricted to the ancestry of a particular changeset. Is there a way
to do this now?
Thanks,
Daniel Holth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFwXldVh4W2pVfoMsRAh8rAKC6bmEKDyiGgHLZ6Vs/mQxl/PSLIgCgoxPU
R7T2GbQA9IhnBflLkgA7gRA=
=RbyZ
-----END PGP SIGNATURE-----
More information about the Mercurial
mailing list