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

Re: [Bug] [cvs2svn] Invalid assumption can lead to 1.1.1.1 revisions being silently dropped.

From: <kfogel_at_collab.net>
Date: 2003-08-14 03:05:18 CEST

"Max Bowsher" <maxb@ukf.net> writes:
> cvs2svn say:
> # The first revision on a vendor branch is always the same as
> # the revision from which the branch sprouts, e.g., 1.1.1.1 is
> # always the same as 1.1, so there's no need to further modify
> # 1.1.1.1 from however it is in the copy from 1.1.
>
> This is false. Example:
>
> 1) Add+commit a file normally
> 2) Import a file of the same name
> There is no guarantee that these were identical
>
> [...]

Thanks, Max. The mistake is mine (and a while ago I also began to
suspect it was not true, but I hadn't gotten around to doing anything
about it yet.)

> I will IssueZilla this, with a summary of any discussion that occurs, in a
> few days time.

I think it's ready to IssueZilla right now. Fortunately, this wrong
assumption is not central to the design of cvs2svn; in fact, the code
will probably get simpler without it.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 14 03:46:16 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.