> From: Branko Čibej [mailto:brane@xbc.nu]
>
> 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.
>
That's only the storage implementation of a link that includes a
revision number. Ref nodes without a revision number just use the path.
> >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.
>
Well, you're the one who said it needed to be optionally tied to a
version.
The only way to sanely handle "links" that always track HEAD is via a
symbolic link because hard links don't behave well in the face of
copies.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 17 17:41:56 2002