[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: Jim Blandy <jimb_at_zwingli.cygnus.com>
Date: 2001-02-12 16:43:51 CET

Greg Stein <gstein@lyra.org> writes:
> On Sat, Feb 10, 2001 at 01:46:55AM -0000, brane@tigris.org wrote:
> >...
> > +COPY: how copied nodes are represented.
> > +
> > +If the header's KIND is "copy", then the node-revision skel represente
> > +a copy of another node, and has the form:
> > +
> > + (HEADER SOURCE-REVISION (NAME ...))
> > +
> > +where SOURCE-REVISION is a filesystem revision, and (NAME ...) is a
> > +list of directory entry names (the path) that identifies the copy
> > +source in this revision. The copy source may not be a mutable node.
>
> $ svn add foo.c
> $ svn cp foo.c bar.c
> $ svn commit
>
> I'd say that the copy source is a mutable node in this scenario :-)

No --- the source of a copy node can never be a mutable node, because
changes to the original mustn't affect the copy. You can't do the
"copy-is-reference" trick if the original is mutable. When we copy
mutable nodes, we really copy them, and record the information some
other way.
Received on Sat Oct 21 14:36:22 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.