git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Pranit Bauva <pranit.bauva@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jul 2016, #06; Tue, 19)
Date: Fri, 22 Jul 2016 08:52:01 -0700	[thread overview]
Message-ID: <xmqqzip9brha.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAFZEwPM7bBV5PxOqA9Zvrq-4M1F83NVXORRKje_fqG74ofUWLQ@mail.gmail.com> (Pranit Bauva's message of "Wed, 20 Jul 2016 21:28:03 +0530")

Pranit Bauva <pranit.bauva@gmail.com> writes:

> 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.

Thanks for an interim report of the current state within the overall
plan.  IIRC, bisect_next (which gets called from bisect_auto_next)
and the functions it calls comprise the bulk of the logic of the
program, so when you are ready to tackle bisect_next, which would
mean that you have done with all the functions it calls, you would
roughly be halfway there.  Nice.


      reply	other threads:[~2016-07-22 15:52 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 ` What's cooking in git.git (Jul 2016, #06; Tue, 19) Pranit Bauva
2016-07-22 15:52   ` Junio C Hamano [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

  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=xmqqzip9brha.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=pranit.bauva@gmail.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).