[p4] cvs2p4 file log preservation

[Gabor Maghera]

Yes, it does.  No information is lost unless you explicitly exclude it from
the conversion via the config file.

The major difference between how it looks between the two tools is that
through Perforce branches get their own name space whereas in CVS they
don't.

Let's say you have one modules, called foobar in CVS which is then converted
to Perforce.

With CVS you specify what branch you would like to check the module out
from: cvs checkout -r test foobar.  This would bring the foobar module down
to your local workspace using the revisions currently on the branch  named
"test".

On the Perforce side, if you have your workspace area mapped to mirror what
is on the server, you may end up with something looking like this in P4V
(and the first time you sync your workspace, these files would show up on
your hard drive as well).

//depot
    /foobar
        /main
        /branch1
        /branch2
        /...
        /test
        /...

As you can see, each branch has its own name space.  This may impact local
performance, especially if you have many branches.  I would encourage users
to trim down their workspace configuration so they only see the branches of
interest to them.

As far as revision history goes, you can use all the bells and whistles P4V
(or p4) has to offer.

Cheers,
Gabor

On Nov 13, 2007 12:53 PM, Thierry Lam <Thierry.Lam at autodesk.com> wrote:

> Does cvs2p4 carry over all the revision log for each file to perforce? If
> so, how does it look on the perforce side, an example will be appreciated?
>
> Thierry
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>