From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>, Nicolas Pitre <nico@cam.org>
Subject: Re: git-fetch fails with error code 128
Date: Fri, 15 Dec 2006 09:46:12 +0000 [thread overview]
Message-ID: <200612150946.14439.andyparkins@gmail.com> (raw)
In-Reply-To: <7vfybiyqk0.fsf@assigned-by-dhcp.cox.net>
On Friday 2006 December 15 00:02, Junio C Hamano wrote:
> Andy, which version of git do you run (I presume they are the
> same version, as you are doing the local fetching), and which
> version of git was the "slightly out of date" repository
> prepared with?
One of them is switched off and in another place at the moment, so this is
from memory:
The initial repository was made with origin/master from a few days ago, that's
the one I've been calling "out-of-date". I cloned that to another computer
and continued adding patches using "1.4.4.1.g3ece-dirty" (the dirt is just my
colour branch patch on top of ba988a83). The fetch is being done back on the
original system which has the newer git but older repository.
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.
On the up-to-date computer I've just made a fresh repository, set .git/config
to point locally at the full repository and ran git-fetch. Interestingly,
that has worked perfectly.
Clearly it is version-specific. I'll do a bit of bisection later and see if I
can nail the problem down.
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
next prev parent reply other threads:[~2006-12-15 9:46 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 [this message]
2006-12-15 21:55 ` Junio C Hamano
2006-12-15 22:13 ` Nicolas Pitre
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=200612150946.14439.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nico@cam.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).