[p4] SCCS to Perforce migration ideas

[Robert Cowham]

"p4 change -f " allows an admin/superuser to change the date/time of a
submitted changelist. This is normally a bad idea, but in the case of
migration from othe systems is usually a good idea.

The net result is a set of changes in your repository with earlier
date/times than other changes with earlier numbers. You need to be aware of
this when reporting. In practice it is seldom a problem since you are
usually talking about different areas of the repository.

The VSStop4 and other conversion scripts do it automatically.

Robert

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Rick 
> Macdonald
> Sent: 21 March 2007 16:03
> To: Perforce Users Mailing List
> Subject: Re: [p4] SCCS to Perforce migration ideas
> 
> Does anybody know if this migration route somehow preserves 
> the dates of the original changes, or does the Perforce 
> history end up looking like it was all done on the day of the 
> migration?
> 
> Rick
> 
> David Weintraub wrote:
> > RCS comes with a script to convert SCCS to RCS. From there, you can 
> > use the standard cvs2p4 script.
> >
> > Take a look at this link for sccstorcs script:
> > <http://www.filewatcher.com/m/SCCStoRCS.shar.11245.0.0.html>
> >
> > On 2/13/07, Rick Macdonald <rickmacd at shaw.ca> wrote:
> >> I've been searching for SCCS to Perforce migration tools, 
> and mostly 
> >> all I've found is people asking the question.
> >>
> >> We've been using Perforce for 8 years but have just merged with a 
> >> company that uses SCCS, CVS and Subversion for the three different 
> >> areas of their system. Potentially, all three would be migrated.
> >>
> >> ...RickM... 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>