Re: git-p4 Question

From: FusionX86 <fusionx86@gmail.com>
Date: Apr 24, 2015, 14:36 UTC
Message-ID: <CAFcBi8-GGxrtm+f7NEf0PmWTkS0m6x2fNPt+y4bopqNLfyvyoQ@mail.gmail.com>
In-Reply-To: <553A0ACF.4000006@diamand.org>

I get an error if I misspell part of the path. For example, if I type //depot/maain instead of //depot/main I will get the "no such files" message you indicated. BUT using incorrect case like //depot/main instead of //depot/Main doesn't return any error, but still completes and creates an empty repo. If it does require correct case, then it should throw an error for //depot/main as well.

Let me know if you need any additional information.

On Fri, Apr 24, 2015 at 3:20 AM, Luke Diamand <luke@diamand.org> wrote:

Show 32 quoted lines

> On 23/04/15 14:42, FusionX86 wrote:
>>
>> Hi Luke,
>>
>> I found a silly mistake I was making in the command I've been using.
>> The folder under the depot should have been capitalized, but it
>> wasn't. Also, I expected that if there was a problem with the command,
>> it would fail with some message instead of creating an empty local git
>> repo.
>
>
> I would expect that as well - it will usually create the empty git repo, but
> it should then fail with an error message, like this:
>
> $ git p4 clone //depot/main/nosuchpath
> Importing from //depot/main/nosuchpath into nosuchpath
> Initialized empty Git repository in
> /home/lgd/p4-hacking/git/nosuchpath/.git/
> Doing initial import of //depot/main/nosuchpath/ from revision #head into
> refs/remotes/p4/master
> p4 returned an error: //depot/main/nosuchpath/...#head - no such file(s).
>
> $ echo $?
> 1
>
> If you get a moment can you send your command output; if it's not doing
> something like the above, then it's a bug.
>
> Thanks!
>
> Luke
>