"Glenn A. Thompson" <gthompson@cdr.net> writes:
> Something else that confused me:
>
> I was reading issues 653 and 654.
>
> I must confess I got stuck on the first sentence of 654.
> "Right now, we use a representation for NodeRevIDs which is unbounded in
> length."
>
> I'm still trying to figure out how NodeRevIDs have unbounded length.
>
> So:
> - "100" is a node id.
> - "100.10" is a node revision id, referring to revision 10 of node 100.
> - "100.10.3" is a node id, referring to the third branch based on
> revision 10 of node 100.
> - "100.10.3.4" is a node revision id, referring to revision 4 of
> of the third branch from revision 10 of node 100.
> And so on.
>
> Does this notation continue on like 100.10.3.4.1.1?
> In looking at some code I thought it could only be the 100.10 or the
> 100.10.3.4 case. I know I saw some code checking
> for those two cases. I can't remember what for.
This is precisely the problem. For example, the node revision for the
trunk/ directory in our source code repository right now is:
1.35.1.192.2.157.1.380.1.28.1.87.1.40.1.109.4.5.3.102.5.3.2.131.\
2.178.1.272.1.24.3.47
*Zoinks!*
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 4 07:35:44 2002