From: Pranit Bauva <pranit.bauva@gmail.com>
To: git@vger.kernel.org
Cc: larsxschneider@gmail.com, chriscool@tuxfamily.org,
christian.couder@gmail.com, Pranit Bauva <pranit.bauva@gmail.com>
Subject: [GSoC Update] Week 3
Date: Mon, 23 May 2016 01:28:23 +0530 [thread overview]
Message-ID: <1463947103-28464-1-git-send-email-pranit.bauva@gmail.com> (raw)
In-Reply-To: <1463334359-14033-1-git-send-email-pranit.bauva@gmail.com>
============================ 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:
* My patches for write_terms()[1] and bisect_log()/voc()[2] have collected
some reviews from Eric Sunshine and Johannes Schindelin.
* As advised in the reviews I have mainly read about git_path() and other
related functions from cache.h
* Also read up on the refs stuff like for_each_ref_in() which Junio
mentioned in the previous update email.
* I have made 2 commits[3] which I am keeping on hold for now as they are
followup for a commit made by Jeff King which I came across while
reading about git_path() and related stuff.
* I have kind of finished writing bisect_clean_state() function. But I
am still working on that as I suspect there might be something missing.
============================ NEXT STEPS ================================
Since I wasn't able to cover up many things this week (which I had
initially planned), those things have now been carried forward along with
a few other stuff. I plan to work more this week and the coming few ones
to make up for the lost time.
Things which would be done in the coming week:
* Finish off (finally) bisect_clean_state() conversion.
* Convert the function bisect_head(). I plan to convert this function and
add it as a subcommand to test the implementation but I will only send
the function without the subcommand to the mailing list because its a
too small function. Though the subcommand version will be put up on
github for everyone to verify whether it is passing the test suite like
I have done it for bisect_voc().
* Convert the function bisect_write(). I plan to convert this function
and add it as a subcommand.
* Investigate why test no. 43 and 44 are failing in t6030 with `|| exit`
in --write-terms.
[1]: http://thread.gmane.org/gmane.comp.version-control.git/294388
[2]: http://thread.gmane.org/gmane.comp.version-control.git/294571
next prev parent reply other threads:[~2016-05-22 20:00 UTC|newest]
Thread overview: 20+ 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 ` Pranit Bauva [this message]
2016-05-30 5:37 ` 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 ` [GSOC Update] Week 9 Pranit Bauva
2016-07-12 22:52 ` [GSOC Update] Week 10 Pranit Bauva
-- strict thread matches above, loose matches on Subject: below --
2017-06-05 20:56 [GSoC] Update: Week 3 Prathamesh Chavan
2017-06-05 22:25 ` Stefan Beller
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=1463947103-28464-1-git-send-email-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.
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).