Re: What's cooking in git.git (Jul 2016, #06; Tue, 19)

From: Pranit Bauva <pranit.bauva@gmail.com>
Date: Jul 20, 2016, 15:58 UTC
Message-ID: <CAFZEwPM7bBV5PxOqA9Zvrq-4M1F83NVXORRKje_fqG74ofUWLQ@mail.gmail.com>
In-Reply-To: <xmqqk2ghdysg.fsf@gitster.mtv.corp.google.com>

Hey Junio,

On Wed, Jul 20, 2016 at 4:24 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 16 quoted lines

> * pb/bisect (2016-07-12) 9 commits
>  - bisect--helper: `bisect_write` shell function in C
>  - bisect--helper: `is_expected_rev` & `check_expected_revs` shell function in C
>  - bisect--helper: `bisect_reset` shell function in C
>  - wrapper: move is_empty_file() and rename it as is_empty_or_missing_file()
>  - t6030: explicitly test for bisection cleanup
>  - bisect--helper: `bisect_clean_state` shell function in C
>  - bisect--helper: `write_terms` shell function in C
>  - bisect: rewrite `check_term_format` shell function in C
>  - bisect--helper: use OPT_CMDMODE instead of OPT_BOOL
>
>  GSoC "bisect" topic.
>
>  Are people happy with this version?  How much of the planned
>  "porting" is finished by this part of the work?  How much more to
>  go?

The current branch contains 30-40 % of the work. I am going to send 3 more functions check_and_set_terms(), bisect_next_check() and bisect_terms() positively by today. After that the work will be around 50-60% complete. After that bisect_start() (I have ported this but it has a bug right now) then bisect_next(), bisect_replay(), bisect_state(), and a few small more.

Regards, Pranit Bauva