From: Nicolas Pitre <nico@cam.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Andy Parkins <andyparkins@gmail.com>, git@vger.kernel.org
Subject: Re: git-fetch fails with error code 128
Date: Fri, 15 Dec 2006 17:13:35 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612151706150.18171@xanadu.home> (raw)
In-Reply-To: <7vy7p8omdh.fsf@assigned-by-dhcp.cox.net>
On Fri, 15 Dec 2006, Junio C Hamano wrote:
> Andy Parkins <andyparkins@gmail.com> writes:
>
> > I hadn't realised it was quite a serious as these responses
> > are making it sound. I'll gather more precise data upon my
> > return home.
> > ...
> > Clearly it is version-specific. I'll do a bit of bisection
> > later and see if I can nail the problem down.
>
> Thanks --- very much appreciated. When it comes to
> inter-repository object transfer, we take compatibility very
> seriously.
I really doubt it is a compatibility problem. The provided error
message may only result from the fact that patch_delta() has returned
NULL.
And since patch-delta is really simple, it doesn't have many reasons for
returning NULL: either the object store on either the remote or local
side is corrupted in which case a git-fsck-objects --full should catch
that, or the system ran out of memory.
next prev parent reply other threads:[~2006-12-15 22:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 23:08 git-fetch fails with error code 128 Andy Parkins
2006-12-14 23:19 ` Shawn Pearce
2006-12-14 23:25 ` Horst H. von Brand
2006-12-15 2:31 ` Nicolas Pitre
2006-12-15 0:02 ` Junio C Hamano
2006-12-15 9:46 ` Andy Parkins
2006-12-15 21:55 ` Junio C Hamano
2006-12-15 22:13 ` Nicolas Pitre [this message]
2006-12-16 0:37 ` Junio C Hamano
2006-12-16 13:29 ` Andy Parkins
2006-12-16 22:12 ` Andy Parkins
2006-12-15 2:25 ` Nicolas Pitre
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=Pine.LNX.4.64.0612151706150.18171@xanadu.home \
--to=nico@cam.org \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).