[Kde-scm-interest] atomicity, again

[Albert Astals Cid]

A Dimecres, 17 de juny de 2009, Johannes Sixt va escriure:
> Boyd Stephen Smith Jr. schrieb:
> > In <200906152027.47623.thiago at kde.org>, Thiago Macieira wrote:
> >> The problem happens when you try to push your nested sub-repositories to
> >> upstream servers. If one of them fails to push, you have to rebase or
> >> merge, which means the SHA-1 of the commit changes. And then you have to
> >> update the link in the parent repository.
> >>
> >> When you push the parent, then maybe that one fails as well to push. You
> >> have to merge and that may cause conflicts (maybe someone pushed an
> >> update to the repository you've just pushed and got to the parent before
> >> you did). You have to fix that manually as well.
> >
> > Oh.  Now I get it.  I'm just used to the git idea of a commit being a
> > local operation.  So, using git/hg terminology, we would like an atomic
> > cross- repository *push*.
>
> That this problem exits at all only shows that the intent that literally
> hundreds of people have push access to the same repository is flawed.

It is not, it only shows tools are not up to what we need. Please stop 
repeating the same nonsense in the hope you will out of our boredom of 
listening the same argument.

Albert