On Fri, Sep 16, 2016 at 11:19 AM, Lars Schneider
wrote:
>
>
> This looks interesting! I ran into the same issue and added a parameter to
> the p4 commands to retry (patch not yet proposed to the mailing list):
>
> On 15 Sep 2016, at 23:17, Ori Rawlings wrote:
>
> Importing a long history from Perforce into git using the git-p4 tool
> can be especially challenging. The `git p4 clone` operation is based
> on an all-or-nothing transactionality guarantee. Under real-world
>
Importing a long history from Perforce into git using the git-p4 tool
can be especially challenging. The `git p4 clone` operation is based
on an all-or-nothing transactionality guarantee. Under real-world
conditions like network unreliability or a busy Perforce server,
`git p4 clone` and `git p4
3 matches
Mail list logo