This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| versioncontrol:atomiccommit [2006/10/07 14:19] – better wikilinks in "monotone implementation" chapter LapoLuchini | versioncontrol:atomiccommit [2022/10/07 01:22] (current) – Move bakeoff stuff under a single namespace KubilayKocak |
|---|
| ===== Monotone Implementation ===== | ===== Monotone Implementation ===== |
| **Supported** | **Supported** |
| (also see [http://venge.net/monotone/wiki/FeatureAtomicCommit monotone:[[/FeatureAtomicCommit|FeatureAtomicCommit]]]) | (also see [[http://venge.net/monotone/wiki/FeatureAtomicCommit|monotone:FeatureAtomicCommit]]) |
| |
| ["Monotone"] commits are atomic and each produces a discrete revision. | [[/Monotone|Monotone]] commits are atomic and each produces a discrete revision. |
| |
| In addition, you can ''%%commit%%'' at any time to record the current state of your workspace safely. Monotone supports (and encourages) multiple //heads//. You don't have to worry about whether your workspace or repository are up to date with respect to other developers' changes, and you don't have to be interrupted by a need to merge your work with other changes before you can commit. Merging happens as a separate step, when you are ready, and you can always go back to the starting point you just committed if the merge turns out to be difficult. | In addition, you can ''%%commit%%'' at any time to record the current state of your workspace safely. Monotone supports (and encourages) multiple //heads//. You don't have to worry about whether your workspace or repository are up to date with respect to other developers' changes, and you don't have to be interrupted by a need to merge your work with other changes before you can commit. Merging happens as a separate step, when you are ready, and you can always go back to the starting point you just committed if the merge turns out to be difficult. |
| |