[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: no revision log on file that was moved here

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Fri, 24 Oct 2008 00:30:09 -0400

Neels J Hofmeyr wrote:
> Ah I see, thanks for explaining. So the directory's log contains all the
> changes made in its subtree, except for all those changes that were once
> made in a different location before their files were moved into the subtree.
>
> Isn't that kind of quirky?

Yes, if you think of it that way, it is quirky. So try instead to think of
it in the way it was intended. 'svn log' abandons the CVS-like paradigm of
the directory being merely a convenient way to address a collection of
first-class file objects, and applies a recognition of the directory has a
first-class object itself.

Let me try a different explanation on you. The directory's logs contain a
record of changes to that directory (subtree). A change to a file in a
directory is, in a sense, a change to the directory -- after the change is
made, the directory subtree looks different, right?. On the other hand, a
change to a file *not* inside that directory subtree is not, in any sense, a
change to the directory. So, the first chance that a file moved into a
directory from outside it has to effect the way that directory looks occurs
at the moment of the move. Changes to that file prior to its relocation
have no effect on the way the directory appears, and so are not considered
as changes to the directory.

Does that explain things a little better?

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-24 06:30:58 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.