Re: preventing accidental commit

Guten Tag Marshall Schor,
am Donnerstag, 6. Juni 2013 um 22:37 schrieben Sie:

> One issue we thought about when considering using .../dev/... was "wasting
> space" in SVN with (potentially multiple) release candidates (which were binary
> artifacts, like compressed Jar files). Because of this, we were trying to avoid
> using .../dev/... for this.

If this is an issue depends on your binary files and your repository
version and configuration. If the files contain a lot of similar data
and just differ e.g. in timestamps in manifest files and your repo is
current enough and has repository sharing enabled, which is the
default, there should be any need to worry too much about wasting
space as subversion will save identical data only once. With
Subversion 1.8 this seems to be enhanced even further to be able to
find duplicates within the same commit, opposed to former commited
data in earlier versions.

> One thing I don't understand about SVN is how the svn copy works when copying
> from one repository location to another, when files already may exist at the
> target spot.

Just test it, I simply copied one folder to an already existing place
and at least TortoiseSVN asked me if I won't to overwrite the target
folder and it simply got committed as replaced.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow