duanemur...@mac.com wrote on Thu, 10 Jul 2014 12:19 -0700:
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-tmp/.
On Jul 12, 2014, at 11:10 AM, Pete Wyckoff p...@padd.com 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
More data points. I have reproduced the problem on
$ git --version
git version 1.8.5.2 (Apple Git-48)
$ python --version
Python 2.7.5
$ uname -a
Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014;
root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
However, it the command is used on a new empty
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 'git-p4-tmp/8031': unknown revision or path not in
the working tree.
Use '--' to separate paths
All local storage.
…Duane
On Jul 10, 2014, at 11:07 AM, Luke Diamand l...@diamand.org 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
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-tmp/.
I noticed that git-p4 would continue if those files were present.
6 matches
Mail list logo