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

Re: git gc gives "error: Could not read..."

From
Stefan Näwe <stefan.naewe@atlas-elektronik.com>
Date
Jun 1, 2015, 10:08 UTC
Message-ID
<556C2F1B.1060508@atlas-elektronik.com>
In-Reply-To
<20150601095850.GD31389@peff.net>
Am 01.06.2015 um 11:58 schrieb Jeff King:
Show 18 quoted lines
> On Mon, Jun 01, 2015 at 11:14:27AM +0200, Stefan Näwe wrote:
> 
>> Maybe this one:
>>
>>    d3038d (prune: keep objects reachable from recent objects)
> 
> Yes, exactly.
> 
>> It would be really helpful if you sent the patch as an attachment.
>> I know that's not the normal wokflow but our mail server garbles every
>> message so that I can't (or don't know how to...) use 'git am' to test
>> the patch, which I'm willing to do!
> 
> It ended up as a patch series. However, you can fetch it from:
> 
>   git://github.com/peff/git.git jk/silence-unreachable-broken-links
> 
> which is perhaps even easier.
Not really in my situation...(but that's another story)

I managed to create patch files by simply copy-and-pasting the message text (and the From:, Date:, and Subject: fields from 'View message source' in Thunderbird...) which I could then 'git am' ;-)

The patches applied (and compiled) cleanly on v2.4.2 and 'git gc' stopped giving me the error message.

So (FWIW):
Tested-by: Stefan Naewe <stefan.naewe@gmail.com>
Anything else I could test ?
Thanks,
  Stefan
-- 
----------------------------------------------------------------
/dev/random says: Windows N'T: as in Wouldn't, Couldn't, and Didn't.
python -c "print '73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')" 
GPG Key fingerprint = 2DF5 E01B 09C3 7501 BCA9  9666 829B 49C5 9221 27AF
Previous: Jeff KingNext: Jeff King
Message 7 of 15 in “git gc gives "error: Could not read..."”
  1. Stefan NäweJun 1, 2015
  2. Jeff KingJun 1, 2015
  3. Stefan NäweJun 1, 2015
  4. Jeff KingJun 1, 2015
  5. Stefan NäweJun 1, 2015
  6. Jeff KingJun 1, 2015
  7. Stefan NäweJun 1, 2015
  8. Jeff KingJun 1, 2015
  9. 0/3 silence missing-link warnings in some casesJeff King, Jun 1, 2015
  10. 1/3 add quieter versions of parse_{tree,commit}Jeff King, Jun 1, 2015
  11. 2/3 silence broken link warnings with revs->ignore_missing_linksJeff King, Jun 1, 2015
  12. 3/3 suppress errors on missing UNINTERESTING linksJeff King, Jun 1, 2015
  13. Junio C HamanoJun 1, 2015
  14. Jeff KingJun 1, 2015
  15. Junio C HamanoJun 1, 2015

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.