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

Re: How to correct Bogus Date on repository

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Wed, 19 Aug 2009 01:00:49 -0500

On Aug 19, 2009, at 00:55, Lorenz 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.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-19 08:02:15 CEST

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.