On Thu, Apr 3, 2008 at 2:02 PM, Dan Stromberg <dstromberglists_at_gmail.com>
> If I run a basic "svn log" command like:
> $ svn log http://eng2/svn/Datallegro/branches/v3.1.4-dev | wc -l
> ...as you can see, I get a tiny number of lines - but there should be
> thousands if svn is going back to the beginning of repository history as I
> keep hearing it's supposed to. And we could really use complete history.
> I get that same short result whether using an svn 1.1.4 client on CentOS
> 4.6, or an svn 1.4.4 client on openSUSE 10.3. In both cases, the clients
> are talking to an svn 1.1.4 server via WebDAV with FSFS backends on CentOS
> I know, 1.1.4 is really old. I doubt my management is going to go for an
> upgrade without a really good reason though. Is there much chance that
> upgrading the subversion (and 3 repositories) on our server to 1.4.6 would
> help "svn log" go back to the beginning of time like it should? Or would it
> at least fix new commits?
The default behaviour of svn is traverse the history of the branch when
doing svn log. So you should have got all the history until the beginning of
time. Please look at the entire content of the 'svn log' and see where it
Did you create the branch using the 'svn copy' command? Or was it populated
from a local copy of source code or something like that? I know that sounds
like something no one would do; but I can not imagine a scenario where svn
will not print the whole history of a branch. Basically if you do "svn log
-v URL --stop-on-copy" and then look at the very last printed revision, you
will be able to tell how the branch was created?
Received on 2008-04-03 23:23:06 CEST