Re: What's cooking in git.git (Mar 2012, #03; Mon, 5)
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 6, 2012, 18:23 UTC
- Message-ID
- <7vty21twqc.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <CACsJy8BRQ63hV5e63yoMVykOMZS3u-VrdCQtvgRGBji4Yzpi4A@mail.gmail.com>
Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:
Show 6 quoted lines
>> I've picked up only bits that deal with "use streaming API instead >> of reading things in core" and minimally fixed them up. These we >> should be able to polish in time. > > 11/11 should be safe to go too. It simply reads config files so that > parse_object() respects core.bigfilethreshold.
Ok.
> I'd rather leave it as is. All new test cases are test_expect_failure, > they should not interrupt "make test". If I slack off, somebody may be > annoyed enough with those known breakages to give me a little push.
That requires us to vet and agree that the conditions marked with expect_failure are indeed breakages, which I would want avoid. It is frustrating for people who has to later "fix" things and find out that the original "bug" was marked without thinking things through.