From: Junio C Hamano <gitster@pobox.com>
To: Ayush Chandekar <ayu.chandekar@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [GSOC] [Newbie] Test Script t6423 Microproject
Date: Mon, 03 Feb 2025 08:45:47 -0800 [thread overview]
Message-ID: <xmqqldun2czo.fsf@gitster.g> (raw)
In-Reply-To: <CAE7as+YC-u84ef=LRP-FB_0ApJbaP6Le6k6QrV58itiGMHsk1Q@mail.gmail.com> (Ayush Chandekar's message of "Sun, 2 Feb 2025 06:23:41 +0530")
Ayush Chandekar <ayu.chandekar@gmail.com> writes:
> Thank you so much for your response!
> I also deeply apologize for the lack of etiquette. I will submit another patch
> which is the same but follows the guidelines.
Nothing to apologize for, and I certainly did not see any lack of
netiquette. Each community has its peculiar procedure, and the
microproject time is an opportunity for both sides, i.e. the
established members of the community and the newcomers, to meet in
the middle and learn to work together better.
Thanks.
prev parent reply other threads:[~2025-02-03 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 0:45 [GSOC] [Newbie] Test Script t6423 Microproject ayu-ch
2025-02-01 1:17 ` Junio C Hamano
2025-02-02 0:53 ` Ayush Chandekar
2025-02-03 16:45 ` Junio C Hamano [this message]
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=xmqqldun2czo.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ayu.chandekar@gmail.com \
--cc=git@vger.kernel.org \
/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 NNTP newsgroup(s).