Re: checkout by date and cvs2svn

J Robert Ray <jrray@imageworks.com> writes:

> Hi folks,
>
> I just had a fellow dev point out to me that checkout by date doesn't
> work in our repository (i.e. svn checkout -r {2004-10-01} http://...).
>
> We have been migrating from cvs on a project-by-project basis, and I
> have been using cvs2svn to import slices of our cvs repository one at
> a time.
>
> As a result, the dates of the revisions in our repository are not
> strictly in chronological order:

We do the exact same thing -- import portions at a time, subtree by
subtree, and our revisions are no longer in chronological order,
either.

I don't see there really being a good solution short of renumbering a
repo by date... but that could get really messy. Imagine this:

/foo/bar - created on 09/12/04, r12
/foo/bar/blip - imported from cvs, dates range from 01/01/01 to
                01/01/03, r13 through r1000

what revision should /foo/bar be created in, if the repo were
restructured and sorted strictly by date? Or would its revision
entirely disappear, perhaps being subsumed by the cvs import dirs?

Perhaps cvs2svn shouldn't be forging dates at all, instead storing
original dates in a cvs2svn:date property or something... especially
if code in svn is making an assumption that revision ordering and date
ordering are the same.

Chip

-- 
Chip Turner                   cturner@redhat.com
                              Red Hat, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org