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

Re: CVS update: subversion/subversion/libsvn_fs structure

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-02-22 07:07:42 CET

On Wed, Feb 21, 2001 at 11:21:05PM -0500, Greg Hudson wrote:
> > I can't tell see what advantage copy nodes have over simply setting
> > a property on the copy that says where it was copied from.
> Oh, people thought of that. The only problem is that properties are
> inherited from one revision to the next, so you'd have to special-case
> those properties or lose information. (And would lose information.
> If node-rev 100.3 and node-rev 100.4 both say they're copies of rev 12
> foo/bar, that *could* be true, or 100.4 *could* be just inheriting
> from 100.3.) Unless we do something special.

Right. And put copies on *which* node?

Recall that the copy destination is just a new entry in the parent directory
pointing at an existing node. Logically, you'd be attaching the property to
the new directory entry.

If you have a copy node, then the property sits there.

And then yes: the inheritance thing. We specifically covered that at the
Chicago meeting. Heck, even before when Branko and I were going around on
how copy history would be recorded.


Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:23 2006

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.