[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 23:57:26 CET

mark benedetto king <mbk@boredom.org> writes:
> The repository's UUID will be updated iff
> the dumpstream contains a UUID and
> @a uuid_action is not equal to @c svn_repos_load_uuid_ignore and
> either the repository contains no revisions or
> @a uuid_action is equal to @c svn_repos_load_uuid_force

Hmmm, I see. That doc is true as far as it goes, it just doesn't say
what will happen if the dumpstream does *not* contain a UUID but
uuid_action is force. Erroring would be compliant; so would silent

> Unfortunately the user-facing documentation, svnadmin help load,
> is less clear:
> Read a 'dumpfile'-formatted stream from stdin, committing
> new revisions into the repository's filesystem. If the repository
> was previously empty, its UUID will, by default, be changed to the
> one specified in the stream. Progress feedback is sent to stdout.
> Valid options:
> --ignore-uuid : ignore the UUID specified in the file.
> --force-uuid : force the repository UUID to be updated.
> My preference would be to change the message to match the existing
> semantics, rather than the other way 'round.

Okay. I don't feel strongly about it either; I've changed the docs to
be clearer about the current behavior.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 12 00:29:10 2003

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