RE: RE: Re: revision numbering (was: Re: Multiple projects in one repository!)

To add more detail in case it's not clear yet. Here's a snippet from IRC
that I hope helps clarify things.

<rassilon> copying foo to bar creates a new NodeID for Bar.
<rassilon> that's not the problem.
<rassilon> Copying foo to bar just copies foo.
<rassilon> All of the sub-things under foo aren't copied.
<rassilon> So foo/A and bar/A still point to the same NodeID,
ChangeSetID
<rassilon> pair
<rassilon> So when you have a change you're making to bar/A you just use
the existing NodeID, and everything is goodness.
<rassilon> (and the new CHangeSetID of course)
<rassilon> But when you then later change foo/A you have to notice that
the NodeID already has a later change on it then what you think it
should.
<rassilon> This means you need to assign yourself a new NodeID.

Bill

----
Do you want a dangerous fugitive staying in your flat?
No.
Well, don't upset him and he'll be a nice fugitive staying in your flat.
 
> -----Original Message-----
> From: Bill Tutt [mailto:rassilon@lyra.org]
> Sent: Friday, May 03, 2002 2:08 PM
> To: 'Glenn A. Thompson'; Subversion Dev list
> Subject: RE: Re: revision numbering (was: Re: Multiple projects in one
> repository!)
> 
> NodeRevisionIDs as discussed in libsvn_fs/structure are changing soon.
> See http://subversion.tigris.org/issues/show_bug.cgi?id=654 for more
> information as to why.
> 
> The new way to identify "NodeRevisions" is by (NodeID, TransactionID).
> 
> NodeID is a monotonically increasing integer. However, due to the
> funky-ness in O(1) copy support you aren't guaranteed to keep the same
> NodeID forever for a given path.
> 
> Yes, this is odd, but SVN is very storage/time efficient for some of
> it's operations and this causes interesting things to fall out in the
> data model.... :)
> 
> Bill
> 
> 
> > -----Original Message-----
> > From: Glenn A. Thompson [mailto:gthompson@cdr.net]
> > Sent: Friday, May 03, 2002 12:18 PM
> > To: Subversion Dev list
> > Subject: Re: revision numbering (was: Re: Multiple projects in one
> > repository!)
> >
> > Hey Guys:
> >
> > Isn't the real juice in the NodeRevisionIDs?
> > Nodes are forever Right? Deleted for not they are forever Right?
> > I guess I assumed, or (read and forgot; so now I assume), that in
> terms of
> > a
> > unique identity to the world at large it would have to be something
> like
> > "Unique ReposID".NodeRevisionID.
> > I view the Revision number as something that can be reset at will.
> The
> > export
> > import process does that right?
> > I wasn't paying close attention to the import/export thread.  Does
it
> lose
> > NodeRevisionIDs?
> >
> > I'm still spinning up, so go easy on me.
> > FYI, I prefer to be beaten down with a wooden bat. No aluminum
please.
> >
> > Thanks,
> > gat
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: dev-help@subversion.tigris.org
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org