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

RE: dump and load question

From: Shawn Matlock <matlocs_at_odscompanies.com>
Date: 2005-12-30 18:56:33 CET

Ryan wrote:
>I don't know how svnadmin load works in this case

svn load only replaces the ID if it's being used on a new repository. And
that can be suppressed.

>but it sure would be nice if you would have gotten a different repository
>unique ID so that you *couldn't* use your old working copies anymore
>and were forced to replace them....

That is exactly what I do not want. If the repository has the same ID as the
working copies, users should not to have to blow away their working copies
when an update would be just as effective.

Something like "update -force" that will move the WC to a specific revision.
Files that were added in later revisions are treated as unversioned. Files
that were changed in a later revision are treated as changed, as are files
that are actually changed. Files that have not been changed are left alone.

The point being an administrator can clean the repository of commits that
were not supposed to happen (importing a .proj file), and users can update a
mostly valid working copy.

Shawn Matlock

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 30 18:58:30 2005

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