From: Eric Wong <e@80x24.org>
To: Alexandre Bique <bique.alexandre@gmail.com>
Cc: git@vger.kernel.org, Ioannis Kappas <Ioannis.Kappas@rbs.com>
Subject: Re: git-svn dies all the time
Date: Sun, 17 Jul 2016 23:20:35 +0000 [thread overview]
Message-ID: <20160717232035.GC8569@starla> (raw)
In-Reply-To: <CAP737oJOGzcgd547R4Qyo832LtGQPZhLtCPS5tr3F8Ot+pxH7w@mail.gmail.com>
Alexandre Bique <bique.alexandre@gmail.com> wrote:
> Hi,
>
> I did by mistake report the bug here:
>
> https://github.com/git/git-scm.com/issues/807#issuecomment-233200404
>
> In short this is a backtrace of git svn rebase crashing in perl, and
> likely because of an out of memory issue. It crashed on my laptop but
> not on my desktop (4G of RAM vs 16G of RAM).
This might be the same bug in SVN Ioannis (cc-ed) told us about
a few weeks ago:
https://public-inbox.org/git/0BCA1E695085C645B9CD4A27DD59F6FA39AAD5CF@GBWGCEUHUBD0101.rbsres07.net/T/
Curious, which version of SVN bindings are you using?
("git svn --version" should tell you)
prev parent reply other threads:[~2016-07-17 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 20:36 git-svn dies all the time Alexandre Bique
2016-07-17 23:20 ` Eric Wong [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=20160717232035.GC8569@starla \
--to=e@80x24.org \
--cc=Ioannis.Kappas@rbs.com \
--cc=bique.alexandre@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).