Re: Be more careful about updating refs
- From
Johannes Sixt <j.sixt@viscovery.net>
- Date
- Jan 17, 2008, 10:52 UTC
- Message-ID
- <478F3367.8050307@viscovery.net>
- In-Reply-To
- <20080117091558.GA8341@hashpling.org>
Charles Bailey schrieb:
Show 9 quoted lines
> I'm assuming that this original patch and the test update turned into > the following commit in master: > > c3b0dec509fe136c5417422f31898b5a4e2d5e02 is first bad commit > > I just thought I should warn you that this seems (git bisect tells me > so) to have caused a failure in t9301-fast-export.sh on my Mac OS X > 10.4.11 machine although I haven't yet had the time to investigate > why.
I observed the same (on Windows). The reason is that above-mentioned commit introduces a call to parse_objects(). But by the time that fast-import calls write_ref_sha1() (and, hence, this new parse_objects()) it has not yet written a pack file, and parse_objects() fails. I don't have a clue how to fix this short of reverting the commit.
-- Hannes