Branko Čibej <brane@xbc.nu> writes:
> This proposal looks fine, except for one detail: there's no way to
> represent revision history as a DAG. Sure, we can't actually create
> forks and joins in the FS now, but our format should support them.
>
> I suggest adding another header, Prev-node-path, that tells us what
> the path to this node was in the previous revision. If the path didn't
> change, it can be omitted. If the node forked, you get several new
> nodes with the same Prev-node-path. If it joined, the new node gets
> more than one Prev-node-path header (so it's not unique).
Your proposal is clear: but the idea of a single node having multiple
immediate ancestors is a "future" concept that doesn't yet exist in
svn_fs.h.
If we *do* add this concept to our filesystem someday, then I say it's
appropriate to add this field to our dumpformat. That's why we're
going to version our dumpformat after all. Version 1 of our format
represents svn 1.0 fs concepts, and will be forward-compatible. I
think that the prev-node-path field should be saved for a future
version of our dumpformat, once our fs actually has this feature.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 30 14:27:33 2002