perforce import

Max Kovgan arcteam.sb at gmail.com
Tue Jun 21 02:56:33 CDT 2011


hi.

Sorry for the long email, not a good start in a ML :)

I did read some of the RTFMing of hg convert extension (didn't dig the
code yet, but I'm close)
Even ran several attempts to do what I want, which is to import:
 * a selected "main" branch off the p4 "depot"
 * a selection of _other_ branches created off that "main" branch
 * keep users commit info

What I'm hoping to achieve is an hg repository with "default" branch
of the contents of main and the other branches inside that repository
When done, I want to see branching/rebasing commit operations viewable
via various annotation and log viewing utils.
Already got "main" imported, authors mapping working,  but I didn't
find a sensible way to import the branching operations, with naming of
the branches.

I hope it is possible using the hg convert
And I hope I'm missing something.
Because our depot is FAT, (several tens of GB on disk), every attempt
I am taking can take a day or even 2.

I don't understand what --branchmap is doing.

small "intro" into perforce concepts:
In perforce there is a concept of "branch mapping" it is a directed
couple <A,B>., i.e. mapping from location A to B, which can be a list
of such couples.
the mapping target is the "branch" location in the intuitive sense. so
people are committing their work into that B location.
once in a while they do "integrations", which is merges to the branch
(a.k.a. "rebase"), and from the branch (a.k.a. "integrations").
in //depot there are various folders, which can be "just folders" or
folders-targets into which there are branch mappings.
The name of the branch doesn't necessarily have to be equal to the
folder in depot which the mapping is mappted to.
i.e. you can have a mapping:
//depot/main/... //depot/myspecialbranch/...

and it can be inside several named "branch mappings"  like:
  * "my-special-branch",
  * "my-not-so-special-branch"
etc.

So, what I  want to understand:
--branchmap is a map of what to what?
depot paths in p4-ish -> branches in mercurialish  ?
OR
"branch mappings names" in p4-speak -> branches in mercurial-speak  ?
OR
something else ?

?

Thanks in advance,
Max.



--
ArcTeam - Architecture Sharedbook


More information about the Mercurial mailing list