From: Shourya Shukla <email@example.com>
Cc: firstname.lastname@example.org, Johannes.Schindelin@gmx.de, email@example.com,
Shourya Shukla <firstname.lastname@example.org>
Subject: [GSoC][PATCH 0/4] t7401: modernize, cleanup and warn
Date: Sun, 26 Jul 2020 19:55:49 +0530 [thread overview]
Message-ID: <email@example.com> (raw)
The current phase of my GSoC project involves porting
'git submodule summary' from shell to C. While doing so, I, along with
my mentors Christian and Kaartic noticed some discrepancies in the test
script when trying to add a couple of tests to it. Though the test works
perfectly for my C port of 'summary', there were some unexpected behaviours
when trying to some tests to it. This patch series addresses these
issues in the test script by modernizing it, cleaning it up and warning
about some other issues.
Chiefly about patch 4/4 (t7401: add a WARNING and a NEEDSWORK),
when trying to write a test for verifying the summary output of
deinitialized submodule, doing a 'git submodule deinit <path>' did not
bear any fruit since the submodule never really got deinitialized.
The deinit documentation states that:
Unregister the given submodules, i.e. remove the whole
submodule.$name section from .git/config together with
their work tree.
Something which was not actually happening in the test. It appeared
that the reason for the deinit issue is that the test script uses
'git add' to add submodules instead of the command 'git submodule add'.
This behaviour also prompted the need to design a new test script to
have a testing of some niche cases such as those stated before, but
this is something that will be covered in the patch series responsible
for porting the 'summary' subcommand to C.
Comments and reviews are appreciated.
Shourya Shukla (4):
t7401: modernize style
t7401: change test_i18ncmp syntax for clarity
t7401: ensure uniformity in the '--for-status' test
t7401: add a WARNING and a NEEDSWORK
t/t7401-submodule-summary.sh | 26 +++++++++++++++++---------
1 file changed, 17 insertions(+), 9 deletions(-)
next reply other threads:[~2020-07-26 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 14:25 Shourya Shukla [this message]
2020-07-26 14:25 ` [PATCH 1/4] t7401: modernize style Shourya Shukla
2020-07-26 14:25 ` [PATCH 2/4] t7401: change test_i18ncmp syntax for clarity Shourya Shukla
2020-07-26 14:25 ` [PATCH 3/4] t7401: ensure uniformity in the '--for-status' test Shourya Shukla
2020-07-26 14:25 ` [PATCH 4/4] t7401: add a WARNING and a NEEDSWORK Shourya Shukla
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).