From: Jeff King <peff@peff.net>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: gitster@pobox.com, normalperson@yhbt.net, git@vger.kernel.org
Subject: Re: git-svn -- out of memory
Date: Mon, 16 Feb 2009 10:39:00 -0500 [thread overview]
Message-ID: <20090216153900.GA22899@coredump.intra.peff.net> (raw)
In-Reply-To: <1234795937.845716.4397.nullmailer@beryx.hq.kred>
On Mon, Feb 16, 2009 at 03:52:17PM +0100, Alfred M. Szmidt wrote:
> Added an extra 20G of swap, still the same error.
You might have to also tweak your ulimit to be able to use that much
memory in a single process. Is this a 64-bit machine?
-Peff
next prev parent reply other threads:[~2009-02-16 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 14:52 git-svn -- out of memory Alfred M. Szmidt
2009-02-16 14:57 ` Sverre Rabbelier
2009-02-16 15:39 ` Jeff King [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-16 14:23 Alfred M. Szmidt
2009-02-16 15:37 ` Jeff King
2009-02-16 9:37 Alfred M. Szmidt
2009-02-16 10:05 ` Junio C Hamano
2009-02-16 13:45 ` Jeff King
2009-02-14 10:40 Alfred M. Szmidt
2009-02-16 0:38 ` Eric Wong
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=20090216153900.GA22899@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=ams@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=normalperson@yhbt.net \
/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).