At 02:44 PM 9/10/2002 +0300, you wrote:
I thought about maintaining a long branchspec which would have a line for
each file, mapping it from V1.0 to the proper place in V2.0. This will solve
the problem, as this branchspec can be used many times with a single
command. However, creating this branchspec seems like a manual, error-prone
job.
I would probably use "p4 filelog -i" to create some information
on the new tree ("filelog -i //depot/v2.0/...") and then use Perl/Python
to break it into
(from-filename, to-filename)
information. Then I'd use a second Perl/Python script to massage that
into a branch mapping.
(And if you're using the mainline model, which you might not at this
point but could move to RIGHT NOW very nicely, you might consider
that the "v2.0" is the new "main codeline" for that model. It's your
choice whether to call the main codeline "main", which I would.)
-Jeff Bowles
6 messages in com.perforce.perforce-user[p4] Non-trivialy-mapped branching an...