[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: General question about webdav and autoversioning

From: Matheus Leite <matheusleite_at_gmail.com>
Date: 2005-06-11 22:02:55 CEST

2005/6/11, Max Bowsher <maxb@ukf.net>:
> Matheus Leite wrote:
> > Hello,
> > I am thinking of creating a autoversioned SVN repository using webdav
> > and a mounted network drive. However I would like to know the
> > following:
> >
> > - SVN normally remembers file renaming and moving accross revisions.
> > Does the same happens with an autoversioned repository? I am afraid
> > that, if someone renames a file, that would be equivalent to deleting
> > and adding a new file, and this could cause a lot of headache.
>
> It all depends on what operations the specific webdav client sends. Most
> good webdav clients will properly do the operation as a move.

I am using WebDrive, and to test its behavior, I renamed a file and
issued a "svn log --verbose" command. Below is the output. It seems
the file got deleted, then added again. Does anyone else has had this
experience with WebDrive?

Autoversioning commit: a non-deltaV client made a change to
/
------------------------------------------------------------------------
r3 | matheus | 2005-06-11 03:15:19 -0300 (sáb, 11 jun 2005) | 2 lines
Changed paths:
   D /foo.doc
   A /bar.doc (from foo.doc:2)

Autoversioning commit: a non-deltaV client made a change to
/bar.doc
------------------------------------------------------------------------

>
> > - What happens if there is a conflict when an autoversioned repository
> > tries to commit? For example, if someone had a local working copy of
> > the repository and commited separatedly, this could potentially cause
> > a conflict.
>
> Could you clarify? I'm not sure exactly what you are asking.

Suppose I have a repositoy on a mounted drive with autoversion
enabled. I could also checkout a separate working copy and make
changes/commit files manually -- for example, making a change to
foo.doc. Then, if someone edits foo.doc on the network drive, the
autocommit *could* fail because the revision is not up to date.

I guess I should check this by myself, anyway :)

>
> Max.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

-- 
------------------------------
Matheus Costa Leite
matheus@mindsatwork.com.br
 
Minds at Work
Tecnologia da Informação
------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jun 11 22:04:42 2005

This is an archived mail posted to the Subversion Users mailing list.