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

[GSoC] Regarding "Convert scripts to builtins"

From
Paul Sebastian Ungureanu <ungureanupaulsebastian@gmail.com>
Date
Mar 18, 2018, 22:15 UTC
Message-ID
<CADzBBBb0KDVJiX2WSNW=vC6b6paWoK=5XrnZNAY+pwpcu-t9JA@mail.gmail.com>
Hello,

I am interested in the "Convert scripts to builtins" project. I have recently started to analyze it better and see exactly what it entails and a few questions came to my mind.

First of all, I find it difficult to pick which scripts would benefit the most by being rewritten. I am thinking of git bisect, git stash and git rebase since these are maybe some of the most popular commands of Git. However, on the other side, scripts like git-rebase--interactive.sh and git-bisect.sh are also subject of other GSoC projects. Should I steer away from these projects or can I consider them?

Secondly, what is too little or too much? On one hand, I do want to do my best and help the Git community as much as I can. On the other hand, I do not want to have too much on my plate and not be able to finish my project. Considering that mentors have already decided that git rebase --interactive and git bisect are enough for two projects, how could I quantify the time required for each command? Looking back at the previous editions of GSoC I noticed that most projects were focused on only one command.

From my research, these are the scripts that could be subject of this project. Which ones do you think could be the best choice for a project of this kind?

 * git/git-add--interactive.perl
 * git/git-archimport.perl
 * git/git-bisect.sh -- there is a project about this
 * git/git-cvsexportcommit.perl
 * git/git-cvsimport.perl
 * git/git-cvsserver.perl
 * git/git-difftool--helper.sh
 * git/git-filter-branch.sh
 * git/git-instaweb.sh
 * git/git-merge-octopus.sh
 * git/git-merge-one-file.sh
 * git/git-merge-resolve.sh
 * git/git-mergetool--lib.sh
 * git/git-mergetool.sh
 * git/git-quiltimport.sh
 * git/git-rebase--am.sh
 * git/git-rebase--interactive.sh -- there is a project about this
 * git/git-rebase--merge.sh
 * git/git-rebase.sh
 * git/git-remote-testgit.sh
 * git/git-request-pull.sh
 * git/git-send-email.perl
 * git/git-stash.sh
 * git/git-submodule.sh -- there was a project about this
 * git/git-svn.perl
 * git/git-web--browse.sh

I look forward to hearing from you. I will also submit a draft of my proposal soon enough.

Best regards, Paul Ungureanu

Next: Christian Couder
Message 1 of 8 in “[GSoC] Regarding "Convert scripts to builtins"”
  1. Paul Sebastian UngureanuMar 18, 2018
  2. Christian CouderMar 19, 2018
  3. Christian CouderMar 19, 2018
  4. Johannes SchindelinMar 21, 2018
  5. Wink SavilleMar 21, 2018
  6. Johannes SchindelinMar 22, 2018
  7. Wink SavilleMar 22, 2018
  8. Johannes SchindelinMar 23, 2018

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.