From: Pranit Bauva <pranit.bauva@gmail.com>
To: git@vger.kernel.org
Cc: christian.couder@gmail.com, chriscool@tuxfamily.org,
larsxschneider@gmail.com, Pranit Bauva <pranit.bauva@gmail.com>
Subject: [GSOC Update] Week 6
Date: Mon, 13 Jun 2016 13:36:56 +0530 [thread overview]
Message-ID: <20160613080656.5013-1-pranit.bauva@gmail.com> (raw)
In-Reply-To: <20160606065301.5228-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:
* bisect_clean_state() function is converted and sent out to the mailing
list which received some useful comments from Eric Sunshine and the
updated version can be found on bisect-reset branch[3].
* I also converted bisect_reset() function and also introduced a file_size()
method which received some useful comments from Eric Sunshine and Torsten
Bogershausen. You can find the whole branch here[3].
* I have also converted bisect_write() and will send it to the mailing list
soon. The branch can be found here[4].
* I also converted is_expected_rev() and check_expected_revs(). I sent
it to the mailing list which collected some useful reviews from Eric
Sunshine. I have updated according to the reviews. I need to confirm it
once before I send it out on the mailing list. You can find the branch
here[3].
* My v2[5] on a cleanup patch to use the function macro GIT_PATH_FUNC is
yet queued on the pu branch.
================================= NEXT STEPS ================================
Things which would be done in the coming week:
* check_and_set_terms(): This function uses the two global variables in the
script namely TERM_GOOD TERM_BAD. I have decided to pass then as arguments.
* get_terms(): This will also introduce a struct to store global variables
namely TERM_GOOD and TERM_BAD.
* bisect_terms().
* bisect_next_check().
[1]: https://github.com/pranitbauva1997/git
[3]: https://github.com/pranitbauva1997/git/pull/13
[4]: https://github.com/pranitbauva1997/git/pull/14
[5]: http://thread.gmane.org/gmane.comp.version-control.git/295524
Regards,
Pranit Bauva
next prev parent reply other threads:[~2016-06-13 8:08 UTC|newest]
Thread overview: 19+ 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 ` Pranit Bauva [this message]
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-26 23:09 [GSoC] Update: Week 6 Prathamesh Chavan
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=20160613080656.5013-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.
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).