So my understanding is that when you specify a date range it gets the
earliest date and the latest date of the range. Then it finds the revision
numbers corresponding to those two revision times and gives you all
revisions listed between those two revision numbers.
Makes sense in theory but has proven to be a little unreliable.
On Mon, Nov 17, 2008 at 5:41 PM, Larry Shatzer, Jr. <larrys_at_gmail.com>wrote:
> On Mon, Nov 17, 2008 at 3:34 PM, Eric White <eric.white07_at_gmail.com>
> > So the problem is with conversion from CVS to SVN? Does this problem
> > up on repositories that have used SVN from the start? Does it happen when
> > you consolidate svn repositories into a single repo?
> > Thanks!
> > Eric
> The problem is when your dates get out of order from the revisions.
> For example, if r100 has a date of 2007, while r1 is of 2008, you get
> into this problem.
> If you do one cvs2svn conversion, and use an empty repository, and do
> not import multiple cvs2svn runs into the same repository, you should
> be fine.
> -- Larry
Received on 2008-11-18 17:54:42 CET