From: Jeff King <peff@peff.net>
To: "Stefan Näwe" <stefan.naewe@atlas-elektronik.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: git gc gives "error: Could not read..."
Date: Mon, 1 Jun 2015 05:58:51 -0400 [thread overview]
Message-ID: <20150601095850.GD31389@peff.net> (raw)
In-Reply-To: <556C2273.4030405@atlas-elektronik.com>
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.
-Peff
next prev parent reply other threads:[~2015-06-01 9:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 7:37 git gc gives "error: Could not read..." Stefan Näwe
2015-06-01 8:14 ` Jeff King
2015-06-01 8:40 ` Stefan Näwe
2015-06-01 8:52 ` Jeff King
2015-06-01 9:14 ` Stefan Näwe
2015-06-01 9:58 ` Jeff King [this message]
2015-06-01 10:08 ` Stefan Näwe
2015-06-01 10:22 ` Jeff King
2015-06-01 9:54 ` [RFC/PATCH 0/3] silence missing-link warnings in some cases Jeff King
2015-06-01 9:56 ` [PATCH 1/3] add quieter versions of parse_{tree,commit} Jeff King
2015-06-01 9:56 ` [PATCH 2/3] silence broken link warnings with revs->ignore_missing_links Jeff King
2015-06-01 9:56 ` [PATCH 3/3] suppress errors on missing UNINTERESTING links Jeff King
2015-06-01 15:03 ` [RFC/PATCH 0/3] silence missing-link warnings in some cases Junio C Hamano
2015-06-01 15:41 ` Jeff King
2015-06-01 16:11 ` Junio C Hamano
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=20150601095850.GD31389@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=stefan.naewe@atlas-elektronik.com \
/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).