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

Re: Repository UUID Implementation

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-01-09 08:30:23 CET

On Thu, Jan 09, 2003 at 12:50:48AM -0600, cmpilato@collab.net wrote:
> Greg Stein <gstein@lyra.org> writes:
> > > Hmm...I don't like it. This a *Repository* UUID, connected in no way
> > > to a versioning filesystem with a stated goal of usefulness outside
> > > the context of Subversion.
> >
> > And a stated goal for recording cross-repository copy/merge history. And to
> > do *that* right, it goes into the filesystem.
> Admittedly, I'm not sure what the big picture is for cross-repos
> copy/merge history. But technically, I don't think that the
> filesystem has a stated goal of recording that data. Subversion does.

To me, the thought process was pretty simple:

1) Does the filesystem record copy/merge history? Yes
2) In the future, would that include a UUID for a source? I'm 95% sure

Thus, I see the UUID as a feature of the filesystem. You could say that "it
cares" :-)

> But then I realize the obvious answer to the question. We use
> rev-props for commit information because that is metadata on a
> per-revision basis.

Agreed. I'm not sure where that came from :-)


ps. making a distinction between "filesystem" and "Subversion" is a bit
strange, honestly. Just what is the filesystem for? :-) The filesystem is
supposed to work for us first, and be "theoretically pure" somewhere below
that. Having the FS have an identity sits quite fine with me.

Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 9 08:29:19 2003

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

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