|
Size: 1166
Comment:
|
Size: 1613
Comment: fix some urls
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| #pragma section-numbers 2 | |
| Line 4: | Line 5: |
| ''Author: Gideon Sireling | '''This extension is not distributed with Mercurial.''' |
| Line 6: | Line 7: |
| Repository: http://code.accursoft.com/mutable-branches/ | ''Author: Gideon Sireling'' |
| Line 8: | Line 9: |
| Issue tracker: http://code.accursoft.com/mutable-branches/issues'' | Repository: https://bitbucket.org/accursoft/mutable-branches/ Issue tracker: https://bitbucket.org/accursoft/mutable-branches/issues <<TableOfContents>> |
| Line 12: | Line 17: |
| The mutable-branches extension allows [[NamedBranches|named branches]] to be renamed, without rewriting history. This is achieved by separating a branch's identity from its name. | The mutable-branches extension allows [[NamedBranches|named branches]] to be renamed, without rewriting history. Renamings are tracked by a file in the working directory. == Installation == Clone the repository to your local hard drive, or simply download [[https://bitbucket.org/accursoft/mutable-branches/raw/tip/mutable-branches.py|mutable-branches.py]]. Then add the following to your ''`mercurial.ini`'' or ''`.hgrc`'': {{{ [extensions] mutable-branches = path/to/mutable-branches.py }}} |
| Line 22: | Line 36: |
| If the user creates a local branch which they do not intend pushing, it can be recorded in `.hg/localbranches`. ''This feature has not yet been implemented.'' | 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. |
Mutable Branches
This extension is not distributed with Mercurial.
Author: Gideon Sireling
Repository: https://bitbucket.org/accursoft/mutable-branches/
Issue tracker: https://bitbucket.org/accursoft/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 or .hgrc:
[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.