Subversion: Partial support. There are implicit changeset that are generated on each commit.What does this mean, and how does this work? (As you can tell, I'm still learning the CVS/Subversion usage paradigm; I've been a longtime build-scripts-on-top-of-SCCS/RCS development manager, and then later Perforce and Visual Source Safe (ugh).) The above statement (from the comparison document at belios.de) is giving me pause, and I'm now considering GNU arch (or any other non-CVS, open-source CM management) instead, even if my first application of a CM system will probably be to manage sets of documents (and not necessarily source code for software applications). Not also that I'm specifically seeking atomically committed and fully transactional Changesets. Thanks for any help with my analysis! -Matt Background/Definition I'm sure I'm preaching to the choir here on the nature of Changesets, but just in case there's any confusion: [A "Changeset" explanation/definition that I found, in case there's dissention on its definition: http://blogs.msdn.com/korbyp/archive/2004/07/15/184442.aspx ] From http://www.gnu.org/software/gnu-arch/tutorial/introduction.html#Introducing_arch :
Changeset Oriented arch doesn't simply "snapshot" your project trees. Instead, arch associates each revision with a particular changeset: a description of exactly what has changed. arch provides changeset oriented commands to help you review changesets, merge trees by applying changesets, examine the history of a tree by asking what changesets have been applied to it, and so forth.