svn log right after commit seems strange

[Curtis Spencer <th...@gmail.com>]

Hi,

I am pretty new to subversion so I don't know if this is proper
behavior.  I do the following

svnprojectroot> touch hi
svnprojectroot> svn add hi
svnprojectroot> svn commit;

For example, now that commit will put me up to revision #43. 

svnprojectroot> svn log
--------------------------------------
r42 
Did some stuff....

It will not show the r43 revision log unless I actually do svn log hi.

However, if I close the terminal, then reopen one, I can run svn log
from within the directory and it will show r43 stuff.

Anyone have any ideas?

Thanks,
Curtis

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn log right after commit seems strange

[Ben Collins-Sussman <su...@collab.net>]

On Sun, 2004-07-11 at 18:05, Curtis Spencer wrote:

> Anyone have any ideas?

Hm, this seems to be a FAQ.

'svn log' operates on a target.  If you don't specify one, it defaults
to '.'.  In other words, you're asking the log command to show every
revision in which '.' (or something inside it) somehow changed.

The problem is that you're asking log for the history of the current
directory at the *old* revision.

Assume your whole working copy is at r42.  Then you commit a file in
'.', which creates r43.  Now your whole working copy is at r42, and the
one file you committed is at r43.  When you run 'svn log', you're asking
for the history of '.'@r42.  So it shows only changes starting at r42,
going backwards in time.   If you were to run 'svn up', the whole
working copy would be brought to HEAD (r43), and 'svn log' on '.'@43
would then show r43 as the first change.





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org