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

RE: "svn commit" followed by "svn log" doesn't show new revision

From: Dale Worley <dworley_at_pingtel.com>
Date: 2004-11-16 23:23:48 CET

After thinking about it some more, I suspect that the answer is this: What
files are in a directory is *not* "the contents of the directory". Whether
a particular file is in a particular directory is controlled by the
existence/non-existence of the file within the revision that is applicable
to the *file*. The information about the directory that is connected to
*its* revision are its permissions (I think), and above all, its properties.

Thus, committing a file addition is not a change to the containing
directory -- it is only a change to the pathname of the file. Thus, the
containing directory need not be up-to-date. But I suspect that if you
wanted to commit a propchange to the directory, it would have to be


-----Original Message-----
From: Niels Skou Olsen [mailto:nso@manbw.dk]

I would be interested in knowing _why_ the commit semantics of directories
and files need to differ. I'm sure there are good reasons. Can anyone here
explain the ideas behind this, or point me to a document or mailing list
thread that covers this?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 16 23:24:40 2004

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

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