All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pranit Bauva <pranit.bauva@gmail.com>
To: git@vger.kernel.org
Cc: chriscool@tuxfamily.org, larsxschneider@gmail.com,
	christian.couder@gmail.com, Pranit Bauva <pranit.bauva@gmail.com>
Subject: [GSOC Update] Week 9
Date: Mon,  4 Jul 2016 01:57:04 +0530	[thread overview]
Message-ID: <20160703202704.9193-1-pranit.bauva@gmail.com> (raw)
In-Reply-To: <20160627071901.4294-1-pranit.bauva@gmail.com>

================================= SUMMARY ==================================
My public git.git is available here[1]. I regularly keep pushing my work so
anyone interested can track me there. Feel free to participate in the
discussions going on PRs with my mentors. Your comments are valuable.


=============================== INTRODUCTION  ==============================
The purpose of this project is to convert the git-bisect utility which partly
exists in the form of shell scripts to C code so as to make it more portable.
I plan to do this by converting each function to C and then calling it from
git-bisect.sh so as to use the existing test suite to test the function which
is converted.

Mentors:
Christian Couder <chriscool@tuxfamily.org>
Lars Schneider <larsxschneider@gmail.com>


================================== Updates =================================
Things which were done in this week:

 * I have converted check_and_set_terms(), bisect_next_check() and
   bisect_terms() and have also sent an RFC[7] to the
   mailing list for discussion which hasn't yet collected any comments from
   the list. My mentors have given their reviews on github and I will soon
   send the final patch series this week.

 * I have partly converted bisect_start() and a few ending parts are left.

 * I have stalled bisect_replay() for now as before I thought I would partly
   convert it and then call bisect_start() from it but then I realized its
   not worth the effort. So I will continue work on this after I finish
   bisect_start().

================================= NEXT STEPS ================================
Things which would be done in the coming week:

 * Finish off bisect_start().

 * Finsh off bisect_start().

 * Finish off bisect_autostart() (small one, wouldn't take much time but it
   depends on bisect_start()).

 * Start with bisect_next().

This has been a slow week as I was meeting a few friends before their college
began and I plan to cover more in the upcoming week as even my semester is
going to start soon and I wouldn't prefer carrying over the work to my
college.

My next semester starts on 18th July.

======================= My Patches (GSoC project only) ======================

 * check_term_format patch[5]. This is in pu branch. The topic is pb/bisect.

 * bisect_write patch[6]. This is the v3 in the series. This has some minor
   nits as provided by Lars and I will send out a re-roll soon. This is also
   in the pu branch and is applied on top of pb/bisect.

 * bisect_terms patch[7]. This is an RFC and open for discussions. It would
   be very helpful if you can review it over github[8] as my mentors have also
   provided some comments.

[1]: https://github.com/pranitbauva1997/git
[3]: https://github.com/pranitbauva1997/git/pull/17
[4]: http://thread.gmane.org/gmane.comp.version-control.git/297266
[5]: http://thread.gmane.org/gmane.comp.version-control.git/295518
[6]: http://thread.gmane.org/gmane.comp.version-control.git/298263
[7]: http://thread.gmane.org/gmane.comp.version-control.git/298279
[8]: 

Regards,
Pranit Bauva

  reply	other threads:[~2016-07-03 20:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-23 20:10 GSoC Project Selected | Incremental Rewrite of git bisect Pranit Bauva
2016-04-24  6:52 ` Johannes Schindelin
2016-04-25 14:39 ` Matthieu Moy
2016-05-08 11:27 ` [GSOC update] Week 1 Pranit Bauva
2016-05-15 17:45   ` [GSOC Update] Week 2 Pranit Bauva
2016-05-15 18:01     ` Matthieu Moy
2016-05-15 19:17       ` Junio C Hamano
2016-05-15 19:11     ` Junio C Hamano
2016-05-15 19:30       ` Pranit Bauva
2016-05-22 19:58     ` [GSoC Update] Week 3 Pranit Bauva
2016-05-30  5:37       ` [GSOC Update] Week 2 Pranit Bauva
2016-05-30  5:45         ` Pranit Bauva
2016-06-06  6:53         ` [GSOC Update] Week 5 Pranit Bauva
2016-06-13  8:06           ` [GSOC Update] Week 6 Pranit Bauva
2016-06-20  7:37             ` [GSOC Update] Week 7 Pranit Bauva
2016-06-27  7:19               ` [GSOC Update] Week 8 Pranit Bauva
2016-07-03 20:27                 ` Pranit Bauva [this message]
2016-07-12 22:52                   ` [GSOC Update] Week 10 Pranit Bauva

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160703202704.9193-1-pranit.bauva@gmail.com \
    --to=pranit.bauva@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=larsxschneider@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.