From: Cesar Eduardo Barros <cesarb@cesarb.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Stack overflow at write_one()
Date: Sat, 19 Nov 2011 19:46:08 -0200 [thread overview]
Message-ID: <4EC823A0.3010603@cesarb.net> (raw)
In-Reply-To: <7vty5zizwn.fsf@alter.siamese.dyndns.org>
Em 19-11-2011 19:08, Junio C Hamano escreveu:
> Already found the real cause (jGit bug) and workaround posted, I think.
I presume the cause then is what was fixed by
http://egit.eclipse.org/w/?p=jgit.git;a=commit;h=2fbf296fda205446eac11a13abd4fcdb182f28d9
?
> See $gmane/185573
That did it, thanks! The patch had an offset, a fuzz, and a reject, but
it was easy to fix by hand.
$ ../git/git gc
Counting objects: 30254, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6614/6614), done.
warning: recursive delta detected for object
fac71dfa0fe8c70cc852099e061c334e2a548eab
warning: recursive delta detected for object
1b730f5b2e0bdb2a2206af8ed30170509e75a2f5
warning: recursive delta detected for object
2f25a87e67fa3a226e367b9e080f11aa90c9f953
warning: recursive delta detected for object
d5e5eefac91788da9a94efe9a15e0b928a77489e
Writing objects: 100% (30254/30254), done.
Total 30254 (delta 24008), reused 28803 (delta 23266)
And after that the repack does not break anymore:
$ ../git/git gc
Counting objects: 30254, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5876/5876), done.
Writing objects: 100% (30254/30254), done.
Total 30254 (delta 24008), reused 30254 (delta 24008)
--
Cesar Eduardo Barros
cesarb@cesarb.net
cesar.barros@gmail.com
next prev parent reply other threads:[~2011-11-19 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 20:27 Stack overflow at write_one() Cesar Eduardo Barros
2011-11-19 21:08 ` Junio C Hamano
2011-11-19 21:46 ` Cesar Eduardo Barros [this message]
2011-11-19 23:30 ` Shawn Pearce
2011-11-20 0:02 ` Cesar Eduardo Barros
2011-11-20 2:00 ` Shawn Pearce
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=4EC823A0.3010603@cesarb.net \
--to=cesarb@cesarb.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.