[Dropbox without pushes] (was: mercurial for dummies (newbies), remote heads etc)

[Uwe Brauer]

>>> "HK" == Harald Klimach <harald at klimachs.de> writes:

   > Hi,
   >> 1. they push,
   >> 
   >> 2. I pull, merge and push back

   > If you don't want them to bother with the merging, why have them push at
   > all? Just pull from their repositories, and push necessary merges back.

   > If this is not possible either let them send the changesets by mail then
   > tell them to pull from your main repository again after your merge, or
   > create "forks" for them at places, where they can push to (one for each)
   > and you can pull from and push back again.

Usually it is said, one should not use dropbox as a repository, in the
sense that pushes and pulls wouldn't work.

But would the following work.

I move my local repository to my local Dropbox folder which is
synchronized with my real Dropbox account.

My colleagues would copy and modify the Dropbox folder and I would try
periodically try to commit their changes.

I could also use the share extension. I tried that once or twice and
found its behavior confusing.

Any comments?

Uwe Brauer 
-------------- 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/20200530/bfa05ca0/attachment.p7s>