> I did think of something which needs to walk around the version tree,
> though: "svn log". Thinking about "svn log" led me to some other
> questions about the current model, though:
> * Is there any internal difference between "svn branch" and
> "svn cp"?
> * Suppose I "svn cp" foo.c to bar.c, and then modify both
> files. If foo.c was at node-revision 1.2 before the copy,
> which file's changes become 1.3 and which changes become
> 22.214.171.124, and how does the database keep track of that?
It's arbitrary. Whoever gets there first gets 1.3. Since we don't
distinguish between copies and references (since the distinction is
meaningless in the absence of hard links), it doesn't matter.
> (Does bar.c immediately point to a 126.96.36.199 revision even
> though there are no differences in contents or properties
> between 188.8.131.52 and 1.2?) Will "svn log foo.c" show
> information about the changes made to bar.c?
svn log takes a revision and filename, and finds a node number. Then
it walks backward from that node number. Walking backward from a node
ID is unambiguous.
Received on Sat Oct 21 14:36:16 2006