From: Junio C Hamano <gitster@pobox.com>
To: Mansi Maanu <mansimaanu8627@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [GSoC] Introduction - Mansi, microproject t7605
Date: Thu, 26 Feb 2026 13:05:58 -0800 [thread overview]
Message-ID: <xmqqv7fjw6yx.fsf@gitster.g> (raw)
In-Reply-To: <CAO_P5U2ePS55_w2OiipW48AwMhvTJZtZnYVJqKuJdXRZhztazg@mail.gmail.com> (Mansi Maanu's message of "Thu, 26 Feb 2026 12:56:47 -0800")
Mansi Maanu <mansimaanu8627@gmail.com> writes:
> My name is Mansi Singh. I am a Master's student in Information Systems
> at Northeastern University (Seattle) with 3+ years of software
> development experience at Nokia Solutions and Grant Thornton, where I
> built automation tools and AI assistants.
>
> I am applying for GSoC 2026 and interested in the "Improve the git
> repo command" project idea.
>
> As my microproject, I replaced old-style 'test -f' path checks with
> test_path_is_file helpers in t/t7605-merge-resolve.sh. All 4 tests
> pass after the change.
>
> Patch submitted via GitGitGadget: https://github.com/gitgitgadget/git/pull/2050
>
> Email: mansimaanu8627@gmail.com
> GitHub: https://github.com/MansiSingh17
>
> Thanks,
> Mansi
> Pronouns: she/her
Can you stick to a single name when you present yourself to the
community? We've seen a patch signed off by "Mansi", sent from a
person with e-mail accout "Mansi Singh" via GitGitGadget, and now an
introduction sent by "Mansi Maanu", signed "Mansi", identifying
hearself as "Mansi Singh".
It is a bit too confising.
I presume that "Mansi Singh" is the most official name you want to
present yourself as to this community? If so, please use that as
the author identity and on the Signed-off-by: line of your patches.
Anyway, welcome to the community.
next prev parent reply other threads:[~2026-02-26 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 20:56 [GSoC] Introduction - Mansi, microproject t7605 Mansi Maanu
2026-02-26 21:05 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-24 5:46 Mansi Maanu
2026-02-25 18:53 ` Lucas Seiki Oshiro
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=xmqqv7fjw6yx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mansimaanu8627@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