[p4] the problems of migrating due to competing keywords ...

Hello all.

I'm in the process of migrating my code from my old SCM to Perforce
(yea!).  What I'm doing is taking about a dozen important snapshots from
my old system, and then adding them to perforce.

The problem is in the keyword substitution.  I don't know if I can
explain it, so I'll example it.

Lets say I've got too files a.c and b.c.  Both have the Revision keyword
in their comments.  Now, in the first snapshot that I export from my old
system, both a.c and b.c are version 10.  So, I check them into
Perforce.  In P4, they now have revision 1.  This makes sense to me.
Now, I check out my second snapshot from the old SCM.  In this snapshot,
a.c hasn't changed (revision 10) and b.c has (revision 11).  Now, when I
ask P4 to find the files that have changed, of course it thinks that
both a.c and b.c have changed.  (It thinks a.c has changed due to the
fact that a diff performed on it returns a delta.)

Should I just resign myself to the fact that perforce is going to think
that in every snapshot I'm migrating that everything has changed?  Or,
is there a way to tell perforce that if a file's contents have changed
only in the area of it's keyword substitution area, that it really
hasn't changed?

Thanks.

JDG




--
Jay Glanville

_______________________________________________
perforce-user mailing list  -  perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user