[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 1957 - trunk/subversion/include trunk/subversion/libsvn_wc

From: Branko Čibej <brane_at_xbc.nu>
Date: 2002-05-17 10:45:54 CEST

Bill Tutt wrote:

>>From: Branko Cibej [mailto:brane@xbc.nu]
>>In the FS, a local reference node would store the FS path (not the URL!)
>>of the target and (optionally) a revision number. If the rev number is
>>absent, the path refers to HEAD. Conflict resolution for ref nodes is
>>the same as for files.
>Indeed, I'd point out here that a local reference node that's tied to a
>revision number should be stored thusly:
>TargetNodeID.TargetCopyID.TargetTxnID TargetPATH
>TargetPATH is only for UI helping purposes, the use of a
>TargetNodeID.TargetCopyID.TargetTxnID is a data retrieval optimization.
I was really thinking of something that behaves more like a symlink
within the FS. What you describe here is indeed a good implementation
for a hard link, but then you can't track HEAD with it if you put the
NodeChangeID of the target in.

>If you hadn't noticed this yet, this is the hard link that people have
>been wanting. :) It even behaves sanely in the face of copies/branches.
Indeed. But it's not very useful for implementing modules, /precisely/
because you can't track HEAD. That's a must.

Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 17 10:47:08 2002

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.