Query: How to perform a shallow p4 convert

[dhruva]

Hello,



> you're doing an hg2hg conversion!), do:
> 
> hg convert --splicemap mymap.txt [repo from step 5] [repo from step 6]
> 
> mymap.txt should have a single line:
> 
> [full sha1 hash of first rev of converted history] [full sha1 hash of 
> initial import ci rev]
> 
> (that is specifying that the parent rev of the first rev of the 
> conversion to be your initial import of root_changeset rev).
> 
> Hope that helps.


Thank you, that helped. Once I tried doing an incremental convert of the p4 repository, the imported change did not attach itself to the tip and created 2 heads! I think it is a problem with the converter. On incremental convert, it should use the current tip as the parent of some other logic to figure out the parent if there are multiple heads. I could use the same approach you have described after each incremental import but that is too much of manual work and cannot be automated.
 For records, git (p4-git) conversions works fine. It automatically continues from where it left off. No need for startrev. The problem with startrev is from the current repo, you will get the last imported change number and not the next change that needs importing. Ideally, the convert should start with startrev+1. Everytime I want to do an incremental convert, I need to locate the change 1 greater than the change at current tip and start.

-dhruva


      See the Web's breaking stories, chosen by people like you. Check out Yahoo! Buzz. http://in.buzz.yahoo.com/