From: Chinmoy Chakraborty <firstname.lastname@example.org> To: Christian Couder <email@example.com>, firstname.lastname@example.org Subject: Re: [GSoC] Draft Proposal (Convert submodule to builtin) Date: Thu, 8 Apr 2021 14:41:38 +0530 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CAP8UFD0RyhnurYdWt1xWF2O-bpk-irSs71+XH1Zd8ghdzRKZ8Q@mail.gmail.com> This is the V2 of the draft proposal after applying the changes suggested by Christian Couder and Kaartik Sivaraam. Thank you for you reviews :). ================================================== Convert submodule to builtin March 2021 ================================================== ##Personal Information## Name - Chinmoy Chakraborty E-mail - firstname.lastname@example.org Github - https://github.com/chinmoy12c Linkedin - https://www.linkedin.com/in/chinmoy12c/ Major - Information Technology Time Zone - IST (UTC+05:30) ================================================= ##Work Environment## I am fluent in C, Java, Python, and Shell script. I use Git as my VCS, Visual Studio Code as my primary code editor, and Kali Linux as my primary OS. ================================================= ##Git Contributions## [Microproject] Replace instances of `the_repository` with ‘r’. (Learning the ropes) Pull request: https://github.com/gitgitgadget/git/pull/915 Mailing List: https://email@example.com/ [column, range-diff] downcase option description Pull request: https://github.com/gitgitgadget/git/pull/920 Mailing List: https://firstname.lastname@example.org/ [Documentation] updated documentation for git commit --date Pull request: https://github.com/gitgitgadget/git/pull/918 Mailing List: https://email@example.com/ ================================================= ##Project Outline## A few components of git, like `git-submodule.sh` are in the form of shell scripts. This causes problems in production code in multiple platforms like windows. The goal of this project is to convert the shell script version of `git-submodule.sh` to portable c code. The end goal would be to completely remove `git-submodule.sh` and rename `builtin/submodule--helper.c` to `builtin/submodule.c` so that the `git submodule` is fully implemented using C. ================================================= ##Why is the project required?## "Issues with the portability of code" The submodule shell script uses shell commands like `echo`, `grep`, `test`, `printf` etc. When switching to non-POSIX compliant systems, one will have to re-implement these commands specifically for the system. There are also POSIX-to-Windows path conversion issues. To fix these issues, it was decided to convert these scripts into portable C code. "Large overhead in calling the command" The commands implemented in shell scripts are not builtins, so they call `fork()` and `exec()` multiple times, hence creating additional shells. This adds to the overhead in using the commands in terms of time and memory. "No access to low-level API" The shell commands don’t have access to low level commands like `git hash-object`, `git cat-file` etc. As these commands are internally required for submodule commands to work, the shell script needs to spawn a separate shell to execute these commands. ================================================= ##How have I prepared?## I have gone through all the previous works and read through their code to make myself accustomed to the intricacies of the code. I have also structured my workflow based on the observation of the previous discussions on those patches, and taken into consideration the issues faced previously. ================================================= ##Previous Work## A large part of the `git submodule--helper.c` has already been converted by Stefan Beller, Prathamesh Chavan in his GSoC project in 2017, and Shourya Shukla in his GSoC project in 2020. This is the list of already ported commands. set-branch set-url summary status init deinit update foreach sync absorbgitdirs ================================================= ##Work to be done## The only command that is left to be ported is `git submodule add`. The previous work on this by Shourya Shukla in GSoC 2020, did not reach a successful merge due to some issues in design and the patch was dropped as it had been stale for long. See: https://github.com/git/git/blob/1861aa482a38ae84f597cede48167ab43e7e50a3/whats-cooking.txt#L1158-L1169 The first and foremost aim of the project will be to finish porting the `add` command. Thereafter, the end goal would be to completely replace the shell script (git-submodule.sh) with an efficient c code. Before porting the `git submodule add` command the initial work would be dedicated to the implementation of small helper functions in the form of small patches, which would be directly used by the `add` command. This workflow is based on the suggestion by Junio C Hamano on the thread: https://firstname.lastname@example.org/. This workflow would help in the following ways: - It would help in sending patches in a small digestible format. - It would help the reviewers easily review those small units of patches in a single sitting. - It would help keep small logical units of code in different clean commits. An additional test tweak would also be required in `t7400-submodule-basic.sh`, to prepend the keyword ‘fatal’ since the command dies out in case of absence of commits as pointed out by Kaartic Sivaraam on the thread: https://email@example.com/. The following helper functions would be required to be implemented - - A function to guess the path name from the repository string. Example prototype: static char *guess_dir_name(const char *repo) Returns the path name. - A function to assure repo is absolute or relative to parent. Example prototype: static char *get_real_repo(const char *repo) Returns the correct repo name. - A function for normalizing path, that is, removing multiple //; leading ./; /./; /../; trailing / . Example prototype: static char *normalize_path(const char *path) - A function to check if the path exists and is already a git repo, else clone it. Example prototype: static int add_submodule(struct add_data *info) `add_data` is a struct which stores the config of the submodule. - A function to set the submodule config properly. Example prototype: static void config_added_submodule(struct add_data *info) - After implementation of all these helper methods, the main `module_add()` function would be implemented using the helper functions listed above as well as those helper functions which are predefined. ================================================= ##Project Timeline## "Present Day - May 17" I’ll utilize this time in exploring the codebase more properly and solving more issues, which would help me properly familiarize myself with the codebase. I’ll also try to structure a more solidified, detailed workflow and come up with a draft patch based on the previous work and discussions. "May 17 - June 7 (Community bonding period)" - Get familiar with the community. - Discuss proper workflow with mentors. - Make changes in the timeline, if necessary. - Discuss the structure of the series of patches. "June 7 - June 25 (Initial coding phase)" - Finish implementation of the helper functions. - Work on a proper structure of the implementation of the `submodule add` command and implement additional helper functions if required. - Update proper documentation of the helper functions. "June 25 - July 5 (Binding the code)" This time would be used to code the main `submodule add` command using all the helper functions implemented in the initial phase of coding. This includes binding all the code together and then completing the command through incremental reviews. Also, the necessary documentation would be updated parallelly. "July 5 - July 12 (Initiate porting of command)" - Discuss how to go about porting the entire submodule script. - Initiate porting of the `git-submodule.sh` script. "July 12 - July 16 (Phase 1 evaluation)" "July 16 - July 26 (Semester exams)" I will be taking my semester examinations during this time. As such, I’ll try to be in touch with the mentors and take out as much time as possible (around 20 hours a week). "July 26 - August 10 (Porting the complete script)" This period would be utilized in the complete conversion of `git-submodule.sh` into c code and combine it with `submodule--helper.c` to make a single `builtin/submodule.c`. As I’ll be completely free from academics during this period, I’ll try to compensate as much time as possible for the above period of July 16 - July 26. "August 10 - August 16 (Final review and evaluation)" - Final review by the mentors. - Apply necessary changes and touch-ups. - Updating documentation, if any left. "August 16 - August 23 (Submission of final report)" Additionally: There are places in the original shell script and c code tagged as `NEEDSWORK`. My aim would be to resolve these issues within the GSoC period if time permits. ================================================= ##Post GSoC## After the GSoC period, I plan to continue my contributions for git and look for other issues to work on. I’d look into the conversion of other commands which are pending conversion, as well as work on the `NEEDSWORK` part of the code (If I’m unable to finish it within the GSoC period itself). I plan on mentoring new contributors to git and help the contributors by doing code reviews and solving their doubts and helping them out. Regards, Chinmoy Chakraborty.
next prev parent reply other threads:[~2021-04-08 9:10 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-01 11:40 Chinmoy Chakraborty 2021-04-02 5:32 ` Bagas Sanjaya 2021-04-02 6:31 ` Christian Couder 2021-04-02 7:05 ` Chinmoy Chakraborty 2021-04-03 14:14 ` Chinmoy Chakraborty 2021-04-05 14:44 ` Christian Couder 2021-04-06 19:53 ` Chinmoy Chakraborty 2021-04-08 9:11 ` Chinmoy Chakraborty [this message] 2021-04-10 12:03 ` Christian Couder 2021-04-02 7:04 ` Chinmoy Chakraborty
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [GSoC] Draft Proposal (Convert submodule to builtin)' \ /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
Code repositories for project(s) associated with this 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).