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

Re: svn commit: rev 4775 - in branches/issue-1037-uuids/subversion: include libsvn_repos

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2003-02-11 22:42:51 CET

mark benedetto king <mbk@boredom.org> writes:
> > Since it's not really a showstopper if the UUID is absent, personally
> > think we shouldn't error, even if the format version is 2. If we're
> > flexible about these things, then maybe we'll never have to upgrade
> > the format version number again :-), our loaders will just DTRT all
> > the time. (Of course, if someone passes --force-uuid and no UUID is
> > found, that has to be an error.)
> I disagree:
> $ rm foo
> rm: cannot remove `foo': No such file or directory
> $ rm -f foo
> $

Bogus analogy, I think. Just because the word "force" is used for the
Unix rm -f flag and in the Subversion "--force-uuid" flag, doesn't
mean they mean the same thing :-).

Am I correct in thinking that --force-uuid means "take the UUID found
in this dump file and set the destination repository's UUID to it"?

If that's what it means, then it might be appropriate to error if no
UUID is available. After all, the user thought they were setting
their repository's identity to some new UUID... but then it didn't
happen, and the user may never know it.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 11 23:14:33 2003

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