From: Pranit Bauva <pranit.bauva@gmail.com>
To: git@vger.kernel.org
Cc: larsxschneider@gmail.com, christian.couder@gmail.com,
chriscool@tuxfamily.org, Pranit Bauva <pranit.bauva@gmail.com>
Subject: [GSOC Update] Week 2
Date: Mon, 30 May 2016 11:07:58 +0530 [thread overview]
Message-ID: <20160530053758.28134-1-pranit.bauva@gmail.com> (raw)
In-Reply-To: <1463947103-28464-1-git-send-email-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 having a segmentation fault which is yet
not fixed by me. I will try this for one more day and then send it to the
list for RFC.
* I also converted is_expected_rev() and check_expected_revs() which also has
segmentation fault.
* I also converted bisect_head() function. I changed the semantics a little
bit. Previously the shell function used to echo the string, now it returns
the value to the caller.
* I investigated why test no. 43 and 44 are failing with t6030 with `|| exit`
in the previous version of the patch but it didn't in the newer one. This
is because the location of .git was hardcoded and thus it created problems
with bare repositories.
* I also sent a cleanup patch for using the marco GIT_PATH_FUNC to create a
function instead of using git_path() because of the benefits described
in the commit message of that change.
================================= NEXT STEPS ================================
Things which would be done in the coming week:
* Finish bisect_clean_state() conversion.
* Finish is_expected_rev() and check_expected_revs() conversion.
* Convert the function bisect_write(). I plan to convert this function and
add it as a subcommand.
* Convert bisect_reset() and add it as a subcommand.
* Convert get_terms() and add the variables TERM_GOOD and TERM_BAD in a struct
in the global state.
Regards,
Pranit Bauva
next prev parent reply other threads:[~2016-05-30 5:43 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 ` Pranit Bauva [this message]
2016-05-30 5:45 ` [GSOC Update] Week 2 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-05-29 20:41 [GSoC] Update: Week 2 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=20160530053758.28134-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).