From: Grant Limberg <glimberg@gmail.com>
Date: Mon, 23 May 2011 16:18:20 GMT
Subject: Re: [git-p4] Trouble importing all perforce branches into git repository
Message-ID: <34E33A18-B9C4-4CA9-B96C-79B0E2BDCD44@gmail.com>
In-Reply-To: <BANLkTi=TCyyS7Q=3BnLcG=yhL_boH=w1XA@mail.gmail.com>

On May 23, 2011, at 3:54 AM, Vitor Antunes wrote:

> Hi Grant,
> 
> I think I saw that happening when there is nothing to import or in
> situations where the parent of a certain branch does not exist.
> 
> Perforce does not strictly require branch definitions to allow a branch
> structure/flow. It is quite possible that you are integrating stuff
> around without using "branch specs". When git-p4 is importing your P4
> database it will look at all branches available in the server, including
> ones from other depots. So it is possible that while you are seeing a
> big list of branches being processed, none apply to the branch structure
> you are trying to import.
> 
> Could you please confirm that you have Perforce branch specs for all
> branches that you are trying to import?
> 
> Thanks,
> Vitor

Vitor, 

The "Branch-foo" that git-p4 is crashing on does have a branchspec in Perforce.  I cannot, however guarantee that branchspecs were correctly created and used for all integrates in the repository.  It was created long before I started working here.  Is there a way to limit --detect-branches to only certain branches that I can ensure do have branchspecs?

- Grant