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

Re: Side effect on merging?

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Tue, 12 Jul 2011 09:32:15 +0100

On 12 July 2011 08:35, durumdara <durumdara_at_gmail.com> wrote:
> Hi!
> Someone knows what side effect I may got if I recreate a repository
> with new content, but a client trying to do something with older
> files?
> I have 3 repositories that have to much size.
> I must delete the old elements from it, because on first time I also
> put all DB files into rep with the source, and we are don't have it
> now.
> I know there is a way to merge, but it seems to be easier to delete
> the repository from the server, recreate, and commit the needed
> elements only.

The way to 'merge' is described in the subversion book and is referred
to as a dump/load cycle. If you recreate the repository you will lose
all history.

> But I don't know what happens with anothers if I do this.
> 1.) svn make error when it is see that repository is not same - this
> is better

If you create a new repository it has a new UUID so the old working
copies will not be able to access it.

> 2.) I got mysterious errors, when svn confuses on differences - this
> is unacceptable

This can only happen if you force the UUIDs to be the same, or if you
always create repositories by copying an empty repository instead of
letting subversion create one.


:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-07-12 10:32:24 CEST

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

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