From: Eric Wong <normalperson@yhbt.net>
To: alan <alan@clueserver.org>
Cc: git@vger.kernel.org
Subject: Re: Git Subversion problem
Date: Thu, 25 Jan 2007 01:54:30 -0800 [thread overview]
Message-ID: <20070125095430.GA24742@localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0701240935330.3282@blackbox.fnordora.org>
alan <alan@clueserver.org> wrote:
> I think I tracked down where my problem with using Git to pull subversion
> repositories came from.
>
> It seems that if the repository has a file larger than what will fit in
> memory, it does not react well. (Yes, I know that you should not check in
> huge data files into a repository, but accidents happen and Subversion
> does not make it easy to remove them.)
>
> I can work around the problem at the moment, but it may be something that
> the person who maintains that chunk of git may want to look at.
Which version of git-svn are you using? Can you try git-svn from
version 1.4.4.4 of git and see if that problem can be reproduced? The
new delta fetching code in the latest git.git master may try to store
the entire file in memory when receiving it over the network.
--
Eric Wong
next prev parent reply other threads:[~2007-01-25 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 17:40 Git Subversion problem alan
2007-01-25 9:54 ` Eric Wong [this message]
2007-01-25 16:54 ` alan
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=20070125095430.GA24742@localdomain \
--to=normalperson@yhbt.net \
--cc=alan@clueserver.org \
--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).