From: Cesar Eduardo Barros <cesarb@cesarb.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Stack overflow at write_one()
Date: Sat, 19 Nov 2011 22:02:04 -0200 [thread overview]
Message-ID: <4EC8437C.6000808@cesarb.net> (raw)
In-Reply-To: <CAJo=hJv2aGEFcMjTPxJsyLerqUn3w3hc3hWnc1ScaDrSGihzyQ@mail.gmail.com>
Em 19-11-2011 21:30, Shawn Pearce escreveu:
> On Sat, Nov 19, 2011 at 13:46, Cesar Eduardo Barros<cesarb@cesarb.net> wrote:
>> 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
>> ?
>
> Yes. The AOSP servers were all updated with the above JGit patch, so
> the servers are no longer sending duplicate objects. But yes, for a
> period of time there were duplicates in the kernel repositories,
> particularly kernal/omap.
So, would an alternative workaround in my situation be to delete
kernel/omap.git and let repo sync recreate it? It seems repo does not
have extra metadata anywhere else, so just removing the directory should
be enough for it to clone again from scratch, hopefully getting a
corrected pack from the server.
--
Cesar Eduardo Barros
cesarb@cesarb.net
cesar.barros@gmail.com
next prev parent reply other threads:[~2011-11-20 0:02 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
2011-11-19 23:30 ` Shawn Pearce
2011-11-20 0:02 ` Cesar Eduardo Barros [this message]
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=4EC8437C.6000808@cesarb.net \
--to=cesarb@cesarb.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.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).