You'll find that if Ben says it, it's probably true.
Anyway, committing -anything- creates a new revision in the REPOSITORY, but
that's not what I was referring to when I said "bump". The working copy
keeps track of the revision of each object contained within, and while
committing a file (or a prop on a file/directory) updates that object to
HEAD, nothing that wasn't committed gets updated to HEAD.
See http://svnbook.red-bean.com/en/1.1/ch08s03.html#svn-ch-8-sect-3.1
(Inside the Working Copy Administration Area) and
http://svnbook.red-bean.com/en/1.1/ch02s03.html#svn-ch-2-sect-3.3 (How
Working Copies Track the Repository) and the section after that, "The
Limitations of Mixed Revisions" esp. the part that says "After completing a
commit to the repository, the freshly committed files and directories are at
a more recent working revision than the rest of the working copy."
Aside note to Ben: in "How Working Copies Track the Repository" the text
refers to files only, such as "each file in a working directory" and
"working file", when there are entries for directories too, and they are
tracked in the same way.
Mark
-----Original Message-----
From: Niels Skou Olsen [mailto:nso@manbw.dk]
Sent: Wednesday, November 17, 2004 3:02 AM
To: Ben Collins-Sussman
Cc: Mark; users@subversion.tigris.org
Subject: Re: "svn commit" followed by "svn log" doesn't show new revision
> On Nov 16, 2004, at 5:09 PM, Mark wrote:
>
>> That's exactly my experience. Committing a file doesn't bump the revnum
>> of the containing directory, just the file.
I believe this statement is not true. See my follow-up to Mark for an
example that shows it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 17 17:08:09 2004