git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-fetch fails with error code 128

From
APAndy Parkins <andyparkins@gmail.com>
Date
Dec 15, 2006, 09:46 UTC
Message-ID
<200612150946.14439.andyparkins@gmail.com>
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
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 10 in “git-fetch fails with error code 128”
  1. Andy ParkinsDec 14, 2006
  2. Shawn PearceDec 14, 2006
  3. Junio C HamanoDec 15, 2006
  4. Andy ParkinsDec 15, 2006
  5. Junio C HamanoDec 15, 2006
  6. Nicolas PitreDec 15, 2006
  7. Junio C HamanoDec 16, 2006
  8. Andy ParkinsDec 16, 2006
  9. Andy ParkinsDec 16, 2006
  10. Nicolas PitreDec 15, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.