From: Arthur <a.foulon@amesys.fr>
To: git@vger.kernel.org
Subject: Re: git-p4 clone @all error
Date: Mon, 5 Nov 2012 02:02:27 -0800 (PST) [thread overview]
Message-ID: <1352109747598-7570575.post@n2.nabble.com> (raw)
In-Reply-To: <20121103231305.GB11267@padd.com>
Hi,
Here is my import :
Importing from //depot@all into XXXXX
Initialized empty Git repository in
/home/arthur/projets_git/XXXXX/XXXXX/.git/
Importing revision 4258 (43%)
Importing new branch depot/DEV_DATA
Resuming with change 4258
Importing revision 5828 (63%)
Importing new branch depot/RELEASE_1.0
Resuming with change 5828
Importing revision 7720 (88%)
Importing new branch depot/RELEASE_1.0.0
Resuming with change 7720
Importing revision 8588 (100%)
Updated branches: DEV_DATA RELEASE_1.0 MAINLINE/02_SubSystem/10_ARINC_429
MAINLINE RELEASE_1.0.0
fast-import failed: error: unable to resolve reference
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
error: Unable to lock
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
error: unable to resolve reference
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
error: Unable to lock
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
error: unable to resolve reference
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
error: Unable to lock
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
error: unable to resolve reference
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
error: Unable to lock
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
error: unable to resolve reference
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
error: Unable to lock
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
error: unable to resolve reference
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
error: Unable to lock
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
error: unable to resolve reference
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429: Not a directory
error: Unable to lock
refs/remotes/p4/depot/MAINLINE/02_SubSystem/10_ARINC_429
git-fast-import statistics:
---------------------------------------------------------------------
Alloc'd objects: 170000
Total objects: 169644 ( 195421 duplicates )
blobs : 92182 ( 186294 duplicates 74565 deltas)
trees : 70889 ( 9127 duplicates 57686 deltas)
commits: 6573 ( 0 duplicates 0 deltas)
tags : 0 ( 0 duplicates 0 deltas)
Total branches: 8 ( 8 loads )
marks: 1024 ( 0 unique )
atoms: 19603
Memory total: 19217 KiB
pools: 12576 KiB
objects: 6640 KiB
---------------------------------------------------------------------
pack_report: getpagesize() = 4096
pack_report: core.packedGitWindowSize = 33554432
pack_report: core.packedGitLimit = 268435456
pack_report: pack_used_ctr = 19803
pack_report: pack_mmap_calls = 65
pack_report: pack_open_windows = 10 / 11
pack_report: pack_mapped = 257715823 / 268009874
---------------------------------------------------------------------
Import crash after importing revision, my import have not files
--
View this message in context: http://git.661346.n2.nabble.com/git-p4-clone-all-error-tp7570219p7570575.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2012-11-05 10:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 10:44 git-p4 clone @all error Arthur
2012-10-31 13:18 ` Arthur
2012-10-31 14:01 ` Thomas Berg
2012-11-03 23:13 ` Pete Wyckoff
2012-11-05 10:02 ` Arthur [this message]
2012-11-05 22:12 ` Pete Wyckoff
2012-11-06 0:25 ` Vitor Antunes
2012-11-06 8:55 ` Arthur
2012-11-06 13:54 ` Vitor Antunes
2012-11-06 14:20 ` Arthur
2012-11-06 18:35 ` Vitor Antunes
2012-11-06 14:03 ` Arthur
2012-11-03 14:09 ` Pete Wyckoff
2012-11-03 23:07 ` [PATCH] git p4: catch p4 describe errors Pete Wyckoff
2012-11-03 23:12 ` Matt Arsenault
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=1352109747598-7570575.post@n2.nabble.com \
--to=a.foulon@amesys.fr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).