From: Pranit Bauva <pranit.bauva@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jul 2016, #06; Tue, 19)
Date: Wed, 20 Jul 2016 21:28:03 +0530 [thread overview]
Message-ID: <CAFZEwPM7bBV5PxOqA9Zvrq-4M1F83NVXORRKje_fqG74ofUWLQ@mail.gmail.com> (raw)
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:
> * 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
next prev parent reply other threads:[~2016-07-20 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 22:54 What's cooking in git.git (Jul 2016, #06; Tue, 19) Junio C Hamano
2016-07-20 8:20 ` Lars Schneider
2016-07-20 11:32 ` [PATCH] t5541: fix url scrubbing test when GPG is not set Jeff King
2016-07-21 6:44 ` Lars Schneider
2016-07-20 15:58 ` Pranit Bauva [this message]
2016-07-22 15:52 ` What's cooking in git.git (Jul 2016, #06; Tue, 19) 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFZEwPM7bBV5PxOqA9Zvrq-4M1F83NVXORRKje_fqG74ofUWLQ@mail.gmail.com \
--to=pranit.bauva@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).