Version Control Repository on a “Cloud”

[Detlev Offenbach]

Hello,

just to add a little piece. How should merge or conflict resolution work on a 
plain cloud drive? Just to mention it, some cloud software is using a VCS 
like GIT in the background. There should be a reason for it.

Detlev

On Monday 11 November 2013, 15:32:24 Pietro Moras wrote:
> >  Having read/write access to a traditional file
> 
> That's
> exactly what I meant:  having red+write rights on a web depot should
> be enough for creating a Mercurial repository BUT, for what I've seen so
> far, it's NOT so easy.
> Anyhow
> I realize that we are having some difficulties understanding each other,
> and discussing seriously; so I'll probably suspend this discussion.
> Thank you all. -
> P.M. Date: Mon, 11 Nov 2013 09:29:51 -0500Subject: Re: Version 
Control
> Repository on a “Cloud”From: swpalmer at gmail.comTo: studio-
pm at hotmail.comCC:
> mercurial at selenic.comHaving read/write access to a traditional file 
system
> is hardly a "strict condition"Version Control is, and has been, a nice and
> handy common policy for decades. This thread reminds me of this Dilbert
> cartoon:http://dilbert.com/strips/comic/2011-01-07/ScottOn Mon, Nov 11,
> 2013 at 7:18 AM, Pietro Moras <studio-pm at hotmail.com> wrote:
> 
> 
> 
> But the real point is another. For what I've seen so far (I've planned a
> Mercurial thorough exploration next year) only specialized providers can
> host a Mercurial Repository (the same with all other VCS' I know). Well,
> why such a strict condition? I'd expect that if there is a storage where I
> can save a Project of whatever nature (provided it can be stored as a 
file)
> the same Project could also be there Version Controlled. Why not? Only 
this
> way, I presume, Version Control could become really a nice and handy 
common
> policy. Couldn't it? I'd welcome your thoughts. Thanks. - P.M.-- 
*Detlev Offenbach*
detlev at die-offenbachs.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20131111/d65347e2/attachment.html>