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

RE: SUGG: Copy overwrite

From: Troy Simpson <troy_at_ebswift.com>
Date: 2005-08-04 06:19:12 CEST

> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: Thursday, 4 August 2005 2:12 PM
> Why not have the secretary mount the repository directly and
> write to it? That's what subversion/webdav define as
> "autoversioning".

We want the secretary to *only* mount the 'Working' folder in the repository
so that #1 the files in 'Current' are not worked on directly, and #2 the
filesystem isn't used to directly copy the 'Current' folder into a subfolder
in the 'Archive' folder (where you subsequently lose all history on the
copied version of the files). Our script ensures the transition from
current-to-archive and working-to-current is done in an orderly fashion.

We will be running the repository differently when we set it up for the
development team - we will be using subversion clients (such as the repo
browser, TSVN, eclipse plugin etc.) and working copies, but for the
not-so-computer-savvy, this is out of the question - especially when this
thing will be setup where temporary contract staff may be updating files in
the repository.

I know that subversion was never meant to work in this way, but it would be
nice if the suggestion was taken seriously and a switch was added to the
copy command to allow forced overwrite.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 4 06:27:27 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.