Re: Perforce checksum mismatch error while importing in svn

On Fri, Sep 20, 2019 at 8:10 AM Kumar20, Mukesh <Mukesh.Kumar20_at_harman.com>
wrote:

> Hi Team,
>
>
> I created a perforce dump using p42svn perl script, it created
> successfully as showing in below screen.
>
Given the numerous historical flaws in Perforce, I'd not bother trying to
preserve history. (I discovered a symlink update commit bug there, and it
made histories quite corrupt.)

Do a clean export to a new workspace, do a clean import, tag it, and
discard the history for the fastest switchover. While history is considered
one of the great features of source control, it's surprisingly useless when
doing a major architectural switchover. Keeping the old Perforce server
around for a few years might be handy if you can do it, but a simple
export/import is usually *much* cleaner and avoids trying to resolve bugs
that may have been in the source repository for years.

Nico Kadel-Garcia