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

"svn log" not reaching revision 1

From: <johan556_at_gmail.com>
Date: 2007-01-31 11:55:03 CET


I tried to run "svn log -v" on the top of one of my projects, and was
surprised that the revisions returned "stopped" at a certain number
(e.g. 901). The revisions shown were then 1209-901, and revision 900-1
seemed to have disappeared. But when I ran "svn log -v" on a
subdirectory of the project I got all revisions 1209-1.

The commands I used were:

    $ cvs log -v http://svn.server/my/proj/trunk # gives 1209-901
    $ cvs log -v http://svn.server/my/proj/trunk/subdir # gives 1200-1

I also tried to give an explicit "-r1209:1" option, but that didn't
change anything.

I have looked at the revisions around 901, suspecting that I might
have done something that Subversion "didn't like". Some of the commits
were reorganizations (e.g. svn mv) of the top directories of the
project. But should such operations really be that harmful?

Other than these observations I have no clue as to what is wrong. Can
anybody help me explain what is going on?

/Johan Holmberg

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 31 11:55:32 2007

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.