versioncontrol:atomiccommit

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
versioncontrol:atomiccommit [2006/09/18 19:15] – git = atomic commits EricAnholtversioncontrol:atomiccommit [2022/10/07 01:22] (current) – Move bakeoff stuff under a single namespace KubilayKocak
Line 14: Line 14:
  
 ===== SVN Implementation ===== ===== SVN Implementation =====
- 
 Atomic commits are fully supported by Subversion.  A single commit either succeeds or fails. Atomic commits are fully supported by Subversion.  A single commit either succeeds or fails.
  
 ===== Hg Implementation ===== ===== Hg Implementation =====
 +It's all atomic.
  
 ===== Git Implementation ===== ===== Git Implementation =====
 It's all atomic. It's all atomic.
 +
 +===== Monotone Implementation =====
 +**Supported**
 +(also see [[http://venge.net/monotone/wiki/FeatureAtomicCommit|monotone:FeatureAtomicCommit]])
 +
 +[[/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.
  
  • versioncontrol/atomiccommit.1158606924.txt.gz
  • Last modified: 2006/09/18 19:15
  • by EricAnholt