Differences between revisions 29 and 30
Revision 29 as of 2013-01-28 16:39:31
Size: 1499
Editor: nesher1
Comment: does not work with 2.5
Revision 30 as of 2013-01-30 09:37:41
Size: 1465
Editor: nesher1
Comment: now compatible with 2.5
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:

<!> Does not yet work with 2.5

Mutable Branches

Author: Gideon Sireling

Repository: http://code.accursoft.com/mutable-branches/

Issue tracker: http://code.accursoft.com/mutable-branches/issues

1. Overview

The mutable-branches extension allows named branches to be renamed, without rewriting history. Renamings are tracked by a file in the working directory.

2. Installation

Clone the repository to your local hard drive, or simply download mutable-branches.py. Then add the following to your mercurial.ini:

[extensions]
mutable-branches = path/to/mutable-branches.py

3. Renaming Branches

To start renaming branches, create a file called .hgbranches in the root of the working directory, and check it in. Each line in .hgbranches consists of a space-delimited pair such as oldBranch newBranch. If the branch name contains spaces, it should be quoted.

There are no changes to Mercurial's UI, other than not scolding the user when they create a new branch.

4. Local Branches

If the user creates a local branch which they do not intend pushing, it can be recorded in .hg/localbranches. Local renamings override repository renamings.

5. Future Development

Other fields could be added to .hgbranches, such as the branch's description or owner.


CategoryExtensionsByOthers

MutableBranches (last edited 2019-08-22 10:56:57 by gidyn)