Ryan Schmidt wrote:
>> Puig, Juan wrote:
>>> I'm getting a connection error from tortoisesvn when going to Show
>>> Log. Apparently there are two
>>> particular revisions which are not available. I went to the
>>> repository server and found this:
>>>
>>>> Svnlook date -r 100 myrep
>>> 2009-08-04 05:23:40 -0300 (Tue, 04 Aug 2009)
>>>> Svnlook date -r 101 myrep
>>> Svnlook: Bogus Date.
>>>> Svnlook date -r 102 myrep
>>> Svnlook: Bogus Date.
>>>> Svnlook date -r 103 myrep
>>> 2009-08-06 11:54:53 -0300 (Thu, 06 Aug 2009)
>>>
>>> [...] but what I need now is to correct this date because each
>>> time I go to show log a get a connection
>>> error when trying to see this two commits.
>>
>> I don't think correcting the commit date will help here, as TSVNs log
>> view has no problems with non-consecutive commit dates (they are only
>> revision property after all).
>>
>> The only point where commit dates are relevant to subversion is if you
>> use the date/daterange syntax to identify revisions.
>>
>> There must be more wrong with this revisions than the commit date.
>
>I don't think the problem is that the dates are nonconsecutive. I
>think the problem is that the contents of the svn:date properties of
>revisions 101 and 102 are not dates. Perhaps they are empty; perhaps
>they are garbage.
I played around with my test repository (fsfs via svnserve - all
clients and server 1.6.4), corrupting files in revprops and/or revs to
various degrees.
I can't provoke a connection error when calling the log viewer.
The log dialog pops up normaly and after some flickering shows an
error describing (mostly) what I did to the repository.
--
Lorenz
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2385161
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-19 12:03:48 CEST