[Dropbox without pushes]

[Uwe Brauer]

Hi 

Thanks for your mail
   > cesar mena <cesar.mena at gmail.com> writes:

   > hi again,

   > come to think of it, it can be simpler than what i suggested in:
   > https://www.mercurial-scm.org/pipermail/mercurial/2020-May/052000.html.

   > it's basically the same as the bundle idea, but we are letting mercurial
   > do its thing!

   > the strategy would be to keep a repo per colleague in dropbox and have
   > them push/pull there. then you can merge onto a central repo that would
   > be in dropbox as well and accessible as pull only to your colleagues.

   > but once again, if i may, keep a non-dropbox copy of the repository on
   > your computer and do your work there. then push to the dropbox one when
   > you are ready to share.  this way, should the dropbox repo become
   > corrupted, you can always re-clone the non-dropbox one.


So if I understand that correctly: say in my dropobox account there will be

    1. Collaboration/colleague1

    2. Collaboration/colleague2

    3. Collaboration/main

    4. In my machine a cloned main repo.

Then the workflow is.

    1. Colleague  pushes only to colleague 1 etc

    2. Colleague pull only from main


So this is basically the same, as everybody having his own named branch, say
in bitbucket (soon helix)

I have to think about it. Thanks for the proposal.

Regards

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/97dc86ca/attachment.p7s>