dropbox

[Uwe Brauer]

>>> "PD" == Pierre-Yves David <pierre-yves.david at ens-lyon.org> writes:

> I am not sure what your concerns is about. Can you clarify ?
> On 1/15/20 9:53 AM, Uwe Brauer wrote:


Sure. Since bitbucket will shutdown its mercurial support, I am in need
of a replacement which allows me to have private mercurial repositories,
for scientific collaboration. Helix is nice, but only allow 5
collaborators for free.

So I though to use Dropbox as poor-man's replacement, with the following
workflow.

I am running on  Linux a dropbox application which synchronize
permanently with my whole Dropbox account.

I create a directory in my dropbox account, say My-Bitbucket.

I push to that directory and give my collaborator write access to the
repository in that directory. He then can clone push and pull.

Anecdotal evidence in stackflow and other places suggests, that because
of the app running in the back, sooner or later the mercurial repository
gets corrupted.

Did I explain my situation in sufficient detail.

Can you comment on that setting?

BTW, I sent a bug report saying that I cannot run make deb any more on
Ubuntu for 16.04 for recent changesets in the default branch. Nobody
answered shall I try to open an issue in heptapod, instead.

Thanks and 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/20200127/aa40cbf8/attachment.p7s>