From: Ephrim Khong <dr.khong@gmail.com>
To: Jeff King <peff@peff.net>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [Bug] git gc with alternates tries accessing non-existing directory
Date: Wed, 18 Mar 2015 12:55:12 +0100 [thread overview]
Message-ID: <550967A0.4000901@gmail.com> (raw)
In-Reply-To: <20150318094232.GA26496@peff.net>
On 18.03.2015 10:42, Jeff King wrote:
> On Wed, Mar 18, 2015 at 09:11:48AM +0100, Ephrim Khong wrote:
>
>> I have a non-bare repository /home/a set up with an alternate to the bare
>> repository /b. Running git gc on /home/a produces below's error
>> [...]
>>> git --version
>> git version 2.3.0
>
> Try v2.3.2. It has b0a4264 (sha1_file: fix iterating loose alternate
> objects, 2015-02-08), which is almost certainly the problem.
Indeed, the message is gone in v2.3.3. Thanks!
- Eph
prev parent reply other threads:[~2015-03-18 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 8:11 [Bug] git gc with alternates tries accessing non-existing directory Ephrim Khong
2015-03-18 9:42 ` Jeff King
2015-03-18 11:55 ` Ephrim Khong [this message]
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=550967A0.4000901@gmail.com \
--to=dr.khong@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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).