[Dropbox without pushes]

[Uwe Brauer]

   > Uwe Brauer <oub at mat.ucm.es> writes:

   > you said it better :)


   > yes, with the added benefit colleagues don't write into other colleagues
   > backends, lessening the chance for dropbox conflicts.

No I mean if I stick to named branches, than we can stay with bitbucket,
my colleagues very surprised, even annoyed by the message

«you cannot push because of anonymous heads»


Without pushing problems, people are ok with mercurial.

That is why dropbox was mentioned.

However this is self-deception at its finest.

The point is, and I think this is a general phenomena, people in a
collaboration think they are working strictly sequential, while in fact
they don't. Because if they worked sequential, then there would be no
anonymous heads.


Mercurial just displays an underlining merging problem, which I am
afraid a lot of people have difficulties to gasp.

And that is why I think all these dropbox solutions have un noticed
merging problems

Uwe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5673 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20200531/c50d0eb8/attachment.p7s>