Cvs files added on the branch converted to svn lacks history ...

Patwardhan, Rajesh wrote:
> We have been using cvs2svn very hapily for the last 4
months. We are
> trying the mock conversion for small and large
repositories and with
> latest --co-internal option we are able to reduce the
conversion time by
> 50%.
> 
> The only problems I see is that
> 
> 1/ A file is added on the branch and then subsequently
merged to the head.
> In cvs you will see that version 1.1 FILE Removed
revision dead since
> the file is initially added on the branch..
> When I look at the converted svn log
> I am not able to see this revision converted from cvs
to svn.

If a file is added on a branch, then CVS adds a version 1.1
to trunk in
state "dead", basically because the branch needs a
place to branch from.
 This revision 1.1 is meaningless because it tells that the
file, which
never existed on trunk, still doesn't exist.  Therefore
cvs2svn 2.0
doesn't bother converting such 1.1 revisions (unless their
log message
contains any nontrivial information).  That is why you don't
see
revision 1.1 in SVN--because it isn't needed and wouldn't
have any
effect if it were included.

> 2/ also we have see that in some cases the file is
deleted and then
> readded back the revision in svn show up only after
file is added.

I don't understand what you mean here.  Would you please be
more
specific, perhaps with an attached ",v" file and
what you think is strange?

Maybe you are referring to the case when the first revision
on a branch
is "dead" then the second revision on the same
branch is alive.  This is
CVS's way of saying that the file did not exist when the
branch was
created, but was added later.  SVN doesn't need the
"dead" revision, so
cvs2svn doesn't include it in the conversion.

Michael

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: users-helpcvs2svn.tigris.org