From: Josh Steadmon <firstname.lastname@example.org>
To: Shourya Shukla <email@example.com>
Cc: firstname.lastname@example.org, email@example.com,
Subject: Re: [PATCH v2 0/3] submodule: port subcommand add from shell to C
Date: Wed, 18 Nov 2020 16:03:33 -0800 [thread overview]
Message-ID: <20201119000333.GI36751@google.com> (raw)
Thank you for this series! Please see the comments below:
On 2020.10.07 13:15, Shourya Shukla wrote:
> Hello all,
> This is the v2 of the patch with the same title, delivered more than a
> month ago as a part of my GSoC. Link to v1:
Since GSoC has ended for the year, I wanted to point out the
firstname.lastname@example.org list, where you can find additional
mentors if you like.
> The changelog is as follows:
> 1. Introduce PATCH[1/3](dir: change the scope of function
> 'directory_exists_in_index()', 2020-10-06). This was done since
> the above mentioned function will be used in the patch that
> 2. There are multiple changes in this commit:
> A. Improve the part which checks if the 'path' given as
> argument exists or not. Implementing Kaartic's
> suggestions on the patch, I had to make sure that the
> case for checking if the path has tracked contents or
> not also works.
> B. Also, wrap the aforementioned segment in a function
> since it became very long. The function is called
> C. Also, use the function 'is_nonbare_repository_dir()'
> instead of 'is_directory()' when trying to resolve
> D. Append keyword 'fatal' in front of the expected output of
> test t7400.6 since the command die()s out in case of
> absence of commits in a submodule.
> E. Remove the extra `#include "dir.h"` from
> 3. Introduce PATCH[3/3] (t7400: add test to check 'submodule add'
> for tracked paths, 2020-10-07). Kaartic pointed out that a test
> for path with tracked contents did not exist and hence it was
> necessary to write one. Therefore, this commit introduces a new
> test 't7400.18: submodule add to path with tracked contents
Generally, we want to avoid describing in detail what the code does;
hopefully, the code can speak for itself. It may be a better use of the
cover letter to describe the motivation for the series as a whole.
Reviewers will not necessarily have background on what you want to
accomplish. We came up with a few factors that might have inspired this
change, but we're not sure which you intended to address:
* Increase efficiency by reducing the number of processes forked and the
use of the shell.
* Make the submodule code easier to maintain (since the project probably
has more C experts than shell experts).
* Improve the user experience with submodules by giving the
submodule-add code access to C internals, and vice versa.
Knowing what you want to accomplish can make it easier for reviewers. Of
course, you'll also want to include important context in your commit
messages as well, so that it's available in the history if future
debugging is necessary.
Thanks again for the series, and please feel free to follow up if you
have any questions
prev parent reply other threads:[~2020-11-19 0:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 7:45 [PATCH v2 0/3] submodule: port subcommand add from shell to C Shourya Shukla
2020-10-07 7:45 ` [PATCH v2 1/3] dir: change the scope of function 'directory_exists_in_index()' Shourya Shukla
2020-10-07 18:05 ` Junio C Hamano
2020-10-12 10:11 ` Shourya Shukla
2020-11-18 23:25 ` Emily Shaffer
2020-10-07 7:45 ` [PATCH v2 2/3] submodule: port submodule subcommand 'add' from shell to C Shourya Shukla
2020-10-07 18:37 ` Junio C Hamano
2020-10-07 22:19 ` Junio C Hamano
2020-10-08 17:19 ` Junio C Hamano
2020-10-09 5:09 ` Junio C Hamano
2020-11-18 23:13 ` Jonathan Tan
2020-11-19 7:44 ` Ævar Arnfjörð Bjarmason
2020-11-19 12:38 ` Johannes Schindelin
2020-11-19 20:37 ` Junio C Hamano
2020-10-07 7:45 ` [PATCH v2 3/3] t7400: add test to check 'submodule add' for tracked paths Shourya Shukla
2020-11-19 0:03 ` Josh Steadmon [this message]
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:
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 \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
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).