|
Size: 1948
Comment: add this page to CategoryRejectedProposal
|
Size: 1166
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #pragma section-numbers 2 | ## page was renamed from BranchRenaming |
| Line 3: | Line 3: |
| {X} This page describes a proposal that was rejected for core Mercurial. However, it may be implemented as a third party extension. | = Mutable Branches = ''Author: Gideon Sireling |
| Line 5: | Line 6: |
| = Branch Renaming = | Repository: http://code.accursoft.com/mutable-branches/ |
| Line 7: | Line 8: |
| A recurring compliant against [[NamedBranches|named branches]] is that the name is permanent. This page describes a backward-compatible proposal to separate a branch's identity from its name. | Issue tracker: http://code.accursoft.com/mutable-branches/issues'' |
| Line 9: | Line 10: |
| <<TableOfContents>> | == Overview == |
| Line 11: | Line 12: |
| == Visioning Branch Names == | 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. |
| Line 13: | Line 14: |
| An .hgbranches file in the working directory will keep a mapping of branch IDs to their names. When a new branch is created, the changeset's branch field will be set to a unique ID. An entry will then be made in .hgbranches, mapping the branch's ID to its name. | == Renaming Branches == |
| Line 15: | Line 16: |
| This is all done behind the scenes, and could be implemented an an extension. There are no changes to Mercurial's UI. | 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. |
| Line 17: | Line 18: |
| == Conflicts == If conflicting changes have been made to .hgbranches on different branches, or if it contains conflicting entries, this will be resolved by the same rules that apply to .hgtags. |
There are no changes to Mercurial's UI, other than not scolding the user when they create a new branch. |
| Line 23: | Line 22: |
| If the user creates a local branch which they do not intend pushing, it can be recorded in .hg/localbranches. Mercurial should warn the user if they attempt to push a changeset whose branch name is recorded in localbranches, and tell them how to move it to .hgbranches. | 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.'' |
| Line 25: | Line 24: |
| == Backwards Compatibility == | == Future Development == |
| Line 27: | Line 26: |
| If a branch ID is not recorded in .hgbranches or .hg/localbranches, the ID will be used as the branch name. Thus, existing branches can be used (and renamed) without any modifications. If the branch is renamed, older clients will continue to use the old name. == Forwards Compatibility == Future development could add other fields to .hgbranches, such as description or owner. == hg-ibranch == The [[http://bitbucket.org/andre_felipe_dias/hg-ibranch|hg-ibranch]] extension implements a similar concept, but uses tip markers instead of .hgbranches. |
Other fields could be added to `.hgbranches`, such as the branch's description or owner. |
| Line 38: | Line 28: |
| CategoryRejectedProposal | CategoryExtensionsByOthers |
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. This is achieved by separating a branch's identity from its name.
2. 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.
3. Local Branches
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.
4. Future Development
Other fields could be added to .hgbranches, such as the branch's description or owner.