Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeffrey Chang <jeffrey.chang@duke.edu>
Cc: git@vger.kernel.org
Subject: Re: git clone out of memory. alternatives?
Date: Fri, 28 Mar 2008 12:55:47 +0100 (CET)	[thread overview]
Message-ID: <alpine.LSU.1.00.0803281250230.3802@racer.site> (raw)
In-Reply-To: <beb5fde90803271929u40a98915ifd05234476ab92f9@mail.gmail.com>

Hi,

On Thu, 27 Mar 2008, Jeffrey Chang wrote:

> I am working with a large-ish git repository set up as a shared 
> repository.  I am the only user of this repository, and I access it over 
> ssh.
> 
> I am running into a problem where I can no longer clone the repository 
> on a new computer.  I get a message that seems to indicate that the 
> machine with the repository is running out of memory.

AFAICT the config variables pack.* (see config.txt) allow to tune the 
packing, even for cloning.

Hth,
Dscho

      parent reply	other threads:[~2008-03-28 11:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28  2:29 git clone out of memory. alternatives? Jeffrey Chang
2008-03-28  3:04 ` Linus Torvalds
2008-03-28 11:55 ` Johannes Schindelin [this message]

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=alpine.LSU.1.00.0803281250230.3802@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jeffrey.chang@duke.edu \
    /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