From: Luke Diamand <luke@diamand•org>
To: FusionX86 <fusionx86@gmail•com>
Cc: Git Users <git@vger•kernel.org>
Subject: Re: git-p4 Question
Date: Fri, 24 Apr 2015 10:20:15 +0100 [thread overview]
Message-ID: <553A0ACF.4000006@diamand.org> (raw)
In-Reply-To: <CAFcBi88ZohscEZXVXbaf+6=ZKJAy9LRfn2-4WT0JV+1RodBTJg@mail.gmail.com>
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
next prev parent reply other threads:[~2015-04-24 9:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 16:41 git-p4 Question FusionX86
2015-04-20 18:23 ` Sam Vilain
2015-04-21 13:23 ` FusionX86
2015-04-20 19:26 ` Luke Diamand
2015-04-21 13:33 ` FusionX86
2015-04-21 16:53 ` Luke Diamand
2015-04-23 13:42 ` FusionX86
2015-04-24 9:20 ` Luke Diamand [this message]
2015-04-24 14:36 ` FusionX86
2015-04-26 22:27 ` Luke Diamand
-- strict thread matches above, loose matches on Subject: below --
2015-04-20 16:29 Fusion Xavier
2007-08-10 2:53 git-p4 question Govind Salinas
2007-08-10 8:06 ` Alex Riesen
2007-08-10 8:10 ` Alex Riesen
2007-08-10 15:17 ` Govind Salinas
2007-08-10 16:25 ` Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=553A0ACF.4000006@diamand.org \
--to=luke@diamand$(echo .)org \
--cc=fusionx86@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox