SUMMARY OF MY PROJECT: Git submodule subcommands are currently implemented by using shell script 'git-submodule.sh'. There are several reasons why we'll prefer not to use the shell script. My project intends to convert the subcommands into C code, thus making them builtins. This will increase Git's portability and hence the efficiency of working with the git-submodule commands. Link to the complete proposal: [1] Mentors: Stefan Beller <sbeller@xxxxxxxxxx> Christian Couder <christian.couder@xxxxxxxxx> UPDATES: As planned for the second week, I continued working on completing the porting of submodule subcommand foreach[2][3][4] and status.[5][6] An updated version of these was added to the mailing list as well. For the submodule-status, I have implemented the suggestions received on the previous patch. But for submodule-foreach, still, some issues are left to be solved. Apart from this, in this week, porting of submodule subcommand sync was also carried out. But instead of adding anymore floating patches on the mailing list, I have started discussing the patch with my mentors itself, so that on the mailing list, the focus would remain with the ported submodule subcommands status and foreach patches. I have also taken up with the submodule subcommand summary for porting. PLAN FOR WEEK-3 (30 May 2017 to 5 June 2017): As suggested by my mentors, in this week, instead of adding more floating patches to the mailing list and porting more submodule subcommand, I would like to polish the existing patches and try to resolve the issues they currently have, eventually aiming for getting them merged. Also, since I have also completed porting of submodule subcommand sync, after reviewing the patches with mentors I'll soon be posting it on the mailing list. Additionally, I will also try to complete porting of submodule-subcommand summary in this week itself. [1]: https://docs.google.com/document/d/1krxVLooWl--75Pot3dazhfygR3wCUUWZWzTXtK1L-xU/ [2]: https://public-inbox.org/git/20170526151713.10974-1-pc44800@xxxxxxxxx/ [3]: https://public-inbox.org/git/20170526151713.10974-2-pc44800@xxxxxxxxx/ [4]: https://public-inbox.org/git/20170526151713.10974-3-pc44800@xxxxxxxxx/ [5]: https://public-inbox.org/git/20170521122711.22021-1-pc44800@xxxxxxxxx/ [6]: https://public-inbox.org/git/20170521122711.22021-2-pc44800@xxxxxxxxx/