From: Luke Diamand <luke@diamand.org>
To: FusionX86 <fusionx86@gmail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: git p4 clone - exclude file types
Date: Wed, 20 May 2015 07:49:01 +0100 [thread overview]
Message-ID: <555C2E5D.70502@diamand.org> (raw)
In-Reply-To: <CAFcBi89XwW48Goaap=OCVQ_CJrNa_hj5+DWtOHGOsrm6jMs-mw@mail.gmail.com>
On 19/05/15 08:38, FusionX86 wrote:
> Thanks Luke, looks like this does work for excluding files when using
> git p4. Great!
>
> Unrelated question...
>
> While using git p4 I have noticed that most of the time the clone/sync
> operations hang and I have to keep retrying. The Perforce depot I'm
> currently working with is larger than I'd like and has a lot of binary
> files which might be the cause. The point it gets to in the clone/sync
> is always random and doesn't ever stop on the same files or file
> types. Sometimes it'll die soon after starting, but other times it
> almost completes and then dies. If I keep retrying, it will eventually
> complete. I haven't been able to narrow down the cause, but I do
> notice that the git-fast-import stops right as the clone/sync dies.
> I'm wondering if git is overwhelmed and terminates. Have you ever seen
> this? Any suggestions?
Running out of memory?
Is this on a 32bit or 64bit system? How much virtual memory do you have?
Luke
next prev parent reply other threads:[~2015-05-20 6:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 17:59 git p4 clone - exclude file types FusionX86
2015-05-18 20:59 ` Luke Diamand
2015-05-19 7:38 ` FusionX86
2015-05-20 6:49 ` Luke Diamand [this message]
2015-05-21 20:49 ` FusionX86
2015-05-21 21:49 ` Luke Diamand
2015-05-22 1:33 ` FusionX86
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=555C2E5D.70502@diamand.org \
--to=luke@diamand.org \
--cc=fusionx86@gmail.com \
--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).