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

log wrong after commit until update

From: Kenneth Porter <shiva_at_sewingwitch.com>
Date: 2005-04-05 01:23:56 CEST

I was trying to figure out when my last merge from a vendor drop was done
by looking at "svn log" but it failed to report my last commit of a merge.
(The previous commit of a merge was reported, leaving me chasing a
non-existent merge error for awhile because I merged from the wrong base
revision.) After some digging around I came across this item in the issue


Based on that I did a "svn update" and all of a sudden I could see several
recent commits that weren't reported before. What's going on here? Why
doesn't "svn commit" result in the WC completely synchronized with the repo?

I looked back through my screen log and an earlier "svn info" shows the WC
at rev r75 and following "svn update" it printed only "At revision 82.".
"svn info" now shows 82.

Is "svn log" not recursive when used against a WC? If not, what's the
proper way to determine all log messages relevant to a complete WC tree?

I'm using 1.1.1 as client on WinXP and subversion-1.1.2-2.3 by way of
Apache on Fedora Core 2.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 5 01:28:47 2005

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.