>> I can try. Indeed, at this revision, the two other branches do not yet
>> exist. But @all will get everything? Last time, I only got head
> Our P4 server has a limitation on the number of lines returned by "p4
> changes" command, so sometimes I have to use @change_start,@change_stop
> instead of @all. You might want to use this range limitation to test
> git-p4 by limiting to a small number of changelists that allows you to
> check if at least one branch is correctly detected.
I didn't know about this. I wanted to start the cloning at some point
in the past, that's why I used the @123456789 notation.
>>> Also, by using that command it means that the following depot paths must
>> Yes, they indeed do.
> In this case the problem should not be in branchList configuration.
>>> I've never used the --use-client-spec, so I'm not sure if that will not
>>> break the branch detection code.
>> I need to do that because if I don't, the depot is clobbed with
>> binaries. Or perhaps if I put some .gitignore stuff, I might not do
> Keep using it, at least for now. If everything else fails we can look at
> this again.
OK, I'll send a mail on Monday (forgot it was the week end tomorrow...)
Information System Engineer, Ph.D.
Music band: http://liliejay.com/
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html