Any Change Creates New Heads?

[Robert Bauck Hamar]

*Giorgos Keramidas:
>On Tue, 28 Apr 2009 18:21:06 -0700, Stephen Rasku <mercurial at srasku.net> wrote:
>Note that the brokenness I mentioned in the CVS case can also be avoided
>with CVS if your development guidelines include a rule that says:
>
>    Only commit from full checkouts and *always* run the test suite from
>    a fully updated workspace tree.

No, it can't. This minimises the risk, but it doesn't avoid it. As CVS 
lacks atomic commits, a full checkout might just as well be a partial 
checkout if someone else is commiting at the same time. See also 
<URL:http://osdir.com/Article203.phtml>.

As Subversion is mentioned, I must say that subversion doesn't fix this 
either, as it allows for mixed revision working copies 
<URL:http://svnbook.red-bean.com/en/1.5/svn.basic.in-action.html#svn.basic.in-action.mixedrevs>, 
and it will happily commit as long as none of the files being commited 
has conflicts.

-- 
Robert Bauck Hamar
USIT/SAPP/GT - Cerebrum
http://www.uio.no/sok?person=hamar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20090429/6973bc14/attachment.pgp