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

Re: Does 'svn log --strict' have a bug?

From: <cmpilato_at_collab.net>
Date: 2003-04-17 03:48:15 CEST

Philip Martin <philip@codematters.co.uk> writes:

> Hello
> If I run
> svn log --strict http://svn.collab.net/repos/svn/branches/fs-schema-changes/
> I only see two revisions, 5146 and 5123, in the output. A search of
> the mailing list reveals that revisions 5121 and 5117 also affected
> that branch, and 5095 was the revision that created the branch. Why
> doesn't the log command show all five revisions?

Um ... because the filesystem is buggy? :-) Our filesystem schema is
*ridiculously* complex, and its test suite pretty much ends where the
real complicated work of dealing with copies begins. I'm not
surprised to find that there is some brokenness. And Tutt's
not-quite-finished work on issue #1003 and the rename stuff only
served to further complicate things. I have an outstanding
high-priority alert in my head to get that code into shape, but to do
so would require my dropping out of society for a large chunk of time,
and that chunk of time is not something that I (or my Collab office
buddies) are really keen on sacrificing.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 17 03:51:19 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.