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

Re: GSoC Project | Improvise git bisect

From
Pranit Bauva <pranit.bauva@gmail.com>
Date
Mar 20, 2016, 16:26 UTC
Message-ID
<CAFZEwPMEDnzv3mLpULOY=7CQZgULx5QsAb_4Pz40iJWzt9HRGg@mail.gmail.com>
In-Reply-To
<alpine.DEB.2.20.1603201628590.4690@virtualbox>

I didn't mention it before, I was thinking to move directly everything from git-bisect.sh to bisect.c . But then I would have to redirect to a shell script. And ultimately remove bisect--helper.c

Your suggestions is a lot better. I could first move individual functions to bisect--helper.c. This would not affect the current status of the project. When I complete this, I can shift all the methods to bisect.c and place it in the directory builtin/. Then I would remove linking of the git-bisect.sh and introduce builtin/bisect.c thus completing the process. When I am writing functions, I am thinking to make some tests which will be copied contents of t/t6030-bisect-porcelain.sh with s/bisect/bisect--helper/g uncommenting tests as I implement more functions. Should I keep these tests restricted to myself or I send it as a patch along with the corresponding function?

Previous: Johannes SchindelinNext: Matthieu Moy
Message 11 of 16 in “GSoC Project | Improvise git bisect”
  1. Pranit BauvaMar 19, 2016
  2. Matthieu MoyMar 19, 2016
  3. Christian CouderMar 19, 2016
  4. Pranit BauvaMar 19, 2016
  5. Stefan BellerMar 19, 2016
  6. Pranit BauvaMar 20, 2016
  7. Pranit BauvaMar 20, 2016
  8. Matthieu MoyMar 20, 2016
  9. Christian CouderMar 20, 2016
  10. Johannes SchindelinMar 20, 2016
  11. Pranit BauvaMar 20, 2016
  12. Matthieu MoyMar 20, 2016
  13. Johannes SchindelinMar 21, 2016
  14. Pranit BauvaMar 21, 2016
  15. Christian CouderMar 21, 2016
  16. Pranit BauvaMar 21, 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.