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

Re: Behavior check: svnadmin load of revisions with no datestamp

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2007-02-26 22:08:31 CET

Daniel Rall wrote:
> On Mon, 26 Feb 2007, C. Michael Pilato wrote:
>> It appears that today if you 'svnadmin load' a dumpfile that contains
>> revision with no svn:date property, the resulting repository will, for those
>> revisions, have that property (set to the time of the commit of the loaded
>> revision).
>> I can't decide if this is a feature or a bug, but I lean toward the latter.
> IMO, this is definitely a bug, since it will result in a repository
> with revision dates and numbers out of sequence, which impacts the
> behavior of some operations which take a date or date range argument
> (e.g. 'svn log -r {START_DATE}:{END_DATE}').
> Subversion expects "svn:date" to be set -- it doesn't consider an
> empty date to be valid data.

Unfortunately, that's entirely untrue. You simply can't make use of
date-based lookups if the dates aren't present. And even if they *are*
present, that's not to say they are in a meaningful order. For example, if
you use cvs2svn to load projects one-at-a-time into a Subversion repository,
the dates will be completely screwy and overlapping.

But I think you misunderstood my question. I am taking for granted that the
ability to have a missing svn:date is *not* a bug. My question is, "In such
a case, should a date suddenly appear just because you dump and load the
repository data?" I think not. *That's* the bug I'm talking about.

C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on Mon Feb 26 22:08:48 2007

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