|
Size: 2146
Comment: new layout using included subpages in table
|
Size: 2314
Comment: +links
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| Suppose you have a repository with a number of changesets which you want to combine into a single changeset. |
Suppose you have a [:Repository:repository] with a number of [:ChangeSet:changesets] which you want to combine into a single changeset. |
| Line 9: | Line 9: |
| mercurial, namely clone, push, pull. | Mercurial, namely [:Clone:clone], [:Push:push], and [:Pull:pull]. |
| Line 12: | Line 12: |
| single head, and you want to combine the last k revisions into a single revision. |
single [:Head:head], and you want to combine the last k [:Revision:revisions] into a single revision. |
| Line 18: | Line 18: |
| Let us furthermore assume the repository has no local changes. | Let us furthermore assume the repository has no [:LocalModifications:local modifications]. |
| Line 20: | Line 20: |
| The strategy is to take advantage of mercurial's support for repositories with more than one head. What we do is create a branch |
The strategy is to take advantage of Mercurial's support for repositories with more than one head. What we do is create a [:Branch:branch] |
| Line 34: | Line 34: |
| This updates the working directory to revision R. Specifically, this means that the contents of the working directory are changed to that of revision R, and that R becomes the parent of the working directory. |
This updates the [:WorkingDirectory:working directory] to revision R. Specifically, this means that the contents of the working directory are changed to that of revision R, and that R becomes the [:Parent:parent] of the working directory. |
| Line 39: | Line 40: |
| This reverts the working directory to its contents at tip. | This reverts the working directory to its contents at [:Tip:tip]. |
| Line 45: | Line 46: |
| At this point, committing these modifications will create a changeset containing all combined changesets between revisions R and R+k. |
At this point, [:Commit:committing] these modifications will create a changeset containing all combined changesets between revisions R and R+k. |
| Line 52: | Line 53: |
Concatenating multiple changesets into one changeset
(See also [:EditingHistory])
Suppose you have a [:Repository:repository] with a number of [:ChangeSet:changesets] which you want to combine into a single changeset.
This can be done as follows using only the basic operations of Mercurial, namely [:Clone:clone], [:Push:push], and [:Pull:pull].
For simplicity, let us assume that the repository in question has a single [:Head:head], and you want to combine the last k [:Revision:revisions] into a single revision.
For concreteness, let us call the base revision R, and the ending revision R+k.
Let us furthermore assume the repository has no [:LocalModifications:local modifications].
The strategy is to take advantage of Mercurial's support for repositories with more than one head. What we do is create a [:Branch:branch] whose root revision is R and which consists of just one changeset (actually it can be multiple changesets, the principle is the same, but for simplicity let us assume one).
Diagramatically, this looks like:
[:/fig1:fig 1] |
[:/fig2:fig 2] |
[:/fig2:fig 3] |
The procedure is as follows.
- hg update R
This updates the [:WorkingDirectory:working directory] to revision R. Specifically, this means that the contents of the working directory are changed to that of revision R, and that R becomes the [:Parent:parent] of the working directory.
- hg revert -r tip --all
This reverts the working directory to its contents at [:Tip:tip]. Since the parent of the working directory is still R, this means that the combined contents of all changesets between R and R+k show up as the modifications in the working directory.
- hg ci -m "Combined changesets between R and R+k"
At this point, [:Commit:committing] these modifications will create a changeset containing all combined changesets between revisions R and R+k.
- hg clone -r tip oldrepo newrepo
- This assumes you want to get rid of your individual changesets (which are a dangling branch in oldrepo) and just keep the combined changeset. newrepo will now just have the combined changeset.