git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[GSOC Update] Week 10

From
Pranit Bauva <pranit.bauva@gmail.com>
Date
Jul 12, 2016, 22:52 UTC
Message-ID
<20160712225210.28803-1-pranit.bauva@gmail.com>
In-Reply-To
<20160703202704.9193-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. Some discussion is happening on github and I will send out the
   patched when the dust settles.
 * I have converted bisect_start() but there is a bug which I am still working
   on.

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

 * Finish off bisect_start().
 * bisect_next() has become a top priority because it would then help
   converting bisect_auto_next() and then it can be called by other important
   functions like bisect_start().
 * Following that I will convert bisect_auto_start()
 * Then bisect_replay().
======================= 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.

============================= Notification ================================== I will be travelling to my university campus from 14th July to 15th July so I won't be available. I will resume my work after that.

[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]: https://github.com/pranitbauva1997/git/pull/16

Regards, Pranit Bauva

Previous: Pranit Bauva
Message 18 of 18 in “GSoC Project Selected | Incremental Rewrite of git bisect”
  1. Pranit BauvaApr 23, 2016
  2. Johannes SchindelinApr 24, 2016
  3. Matthieu MoyApr 25, 2016
  4. [GSOC update] Week 1Pranit Bauva, May 8, 2016
  5. [GSOC Update] Week 2Pranit Bauva, May 15, 2016
  6. Matthieu MoyMay 15, 2016
  7. Junio C HamanoMay 15, 2016
  8. Junio C HamanoMay 15, 2016
  9. Pranit BauvaMay 15, 2016
  10. [GSoC Update] Week 3Pranit Bauva, May 22, 2016
  11. [GSOC Update] Week 2Pranit Bauva, May 30, 2016
  12. Pranit BauvaMay 30, 2016
  13. [GSOC Update] Week 5Pranit Bauva, Jun 6, 2016
  14. [GSOC Update] Week 6Pranit Bauva, Jun 13, 2016
  15. [GSOC Update] Week 7Pranit Bauva, Jun 20, 2016
  16. [GSOC Update] Week 8Pranit Bauva, Jun 27, 2016
  17. [GSOC Update] Week 9Pranit Bauva, Jul 3, 2016
  18. [GSOC Update] Week 10Pranit Bauva, Jul 12, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.