[Kde-scm-interest] atomicity, again

[Thiago Macieira]

Thomas Zander wrote:
>On Monday 15. June 2009 21.11.50 Thomas Capricelli wrote:
>> I remember that one of the requirements that both git and mercurial
>> could not fulfill 'easily' was atomicity of commits across several
>> repositories
>
>And no tool we every used so far had this feature, so its not really a
>requirement. More a "may be nice to have".
>Though I could see how its actually more hassle than its worth to many.

Well, with SVN it just worked differently because there was a global 
repository revision number. Any commit you made was atomic to the entire 
repository.

The issues with that were different, though. For example, since you aren't 
forced to fetching the latest changes before committing, a commit can 
always break the repository: if between your last "svn up" and the commit, 
someone else committed to files you're not touching.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20090616/9648218d/attachment.sig