From: Patrick Steinhardt <ps@pks.im>
To: Aishwarya Narayanan <aishnana.03@gmail.com>
Cc: Karthik Nayak <karthik.188@gmail.com>, git@vger.kernel.org
Subject: Re: GSoC 2024
Date: Tue, 26 Mar 2024 12:22:30 +0100 [thread overview]
Message-ID: <ZgKv9sZ6shfqym2P@tanuki> (raw)
In-Reply-To: <CAHCXyj2a5QFO+fDekR0sQuyFLocucMQeuABxG=6g1X92_cEkpA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2132 bytes --]
On Tue, Mar 26, 2024 at 02:33:59PM +0530, Aishwarya Narayanan wrote:
> Dear Git Project Maintainers,
>
> Assistance Needed: Locating Test Script for Addressing Git's Exit Code
> Suppression. I hope this email finds you well. My name is Aishwarya,
> and I am reaching out to seek assistance with a microproject I am
> working on within the Git project.
Please not that top-posting is discouraged on the Git mailing list [1].
> As part of my efforts to contribute to the Git project, I am currently
> focusing on addressing the suppression of Git's exit code in test
> scripts, as outlined in the project's microproject ideas.
> Specifically, I aim to identify a test script within the t directory
> where Git's exit code may be inadvertently suppressed.
>
> While I have attempted to locate such a test script independently, I
> have encountered challenges in identifying a suitable candidate.
> Therefore, I am reaching out to request guidance from the project
> maintainers in locating a test script where this issue needs to be
> addressed.
> I tried commands that included:
> grep -Er "git .* \|" t/, grep -R "git .* |" t/, findstr /s /i /p "git .* |" *.sh
>
> Could you please provide any insights or guidance on identifying a
> test script within the t directory that exhibits the suppression of
> Git's exit code? Any pointers or suggestions would be greatly
> appreciated.
>
> Additionally, if there are specific criteria or patterns that I should
> look for when identifying such test scripts, please let me know, and I
> will ensure to align my search accordingly.
The command proposed by Karthik (which is also part of your pipeline
above) does result in several matches in "t/", some of which are actual
good candidates for a micro project. Did you scan through these matches?
The microprojects page at [2] should give you a good idea for what to be
on the lookout for as it explains the issue as well as highlighting some
patterns to watch out for.
Patrick
[1]: https://www.mediawiki.org/wiki/Mailing_list_etiquette
[2]: https://git.github.io/SoC-2024-Microprojects/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-26 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 6:57 GSoC 2024 Aishwarya Narayanan
2024-03-25 17:45 ` Karthik Nayak
2024-03-26 9:03 ` Aishwarya Narayanan
2024-03-26 11:22 ` Patrick Steinhardt [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-04 6:01 Aishwarya Narayanan
2024-03-04 8:37 ` Christian Couder
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZgKv9sZ6shfqym2P@tanuki \
--to=ps@pks.im \
--cc=aishnana.03@gmail.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).