On Jul 12, 2014, at 11:10 AM, Pete Wyckoff wrote:
>> Some additional investigation.
>>
>> I am working in a copy of a repository that was originally used to pull the
>> data
>> from Perforce. As part of my experiments to figure out this problem, I
>> deleted
>> the contents of .git/git-p4-t
git-fast-import is not writing a commit even after a checkpoint/progress
command.
See my previous message "git p4 diff-tree ambiguous argument error".
The error in git-p4 is caused by git not writing the commit even after
git-fast-import has been given a checkpoint and progress command.
On in
the sync is running.
That seems significant.
I expect git-p4 to crash again on a new commit that is not in .git/git-p4-tmp/.
Then I have to start the 8-12 hour process over again (did I mention 70k
commits?).
…Duane
On Jul 10, 2014, at 11:08 AM, Duane Murphy wrote:
> All local stor
All local storage.
…Duane
On Jul 10, 2014, at 11:07 AM, Luke Diamand wrote:
> Is this using NFS, or local storage?
>
>
>
> On 10/07/14 18:30, Bill Door wrote:
>> $ git p4 sync --detect-branches --import-labels //main@all
>> ... Lots of useful information elided
>> fatal: ambiguous argument
4 matches
Mail list logo
