Tracy R Reed wrote:
David Brown wrote:
Because with atomic commits, individual files don't have version numbers.
The versioning is done over the entire tree. With this setup, keyword
expansion makes a lot less sense, since every time you commit, the
"version" number associated with each file would change.
Ah...isn't this how svn works also? ISTR that when anything in the tree
changes the version number of everything above all the way to the root
changes also.
No. If you examine the "version number" associated with a specific file
in SVN, it doesn't change.
Even if the "repository version number" is 189--each individual file has
its own version number. So, file1.c is number 89, file2.c is number
110, file3.c is number 146, and only file4.c which you just touched has
a version number of 189. Consequently, you can get a commit that fails
in SVN and yet some of the files had their version numbers updated.
Very annoying to unwind.
Again, these are fundamental architectural decisions. Specifically what
the version systems regard as "atomic".
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
