All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Aishwarya Narayanan <aishnana.03@gmail.com>
Cc: git@vger.kernel.org, karthik nayak <karthik.188@gmail.com>
Subject: Re: GSoC 2024 [PATCH]
Date: Wed, 27 Mar 2024 10:47:25 +0100	[thread overview]
Message-ID: <ZgPrLXjB5mVXitXu@tanuki> (raw)
In-Reply-To: <CAHCXyj3Now+ZrA+w+L-sQAtAMZ8REru=3uF_Y3Xdt=7CSf=pYQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]

On Wed, Mar 27, 2024 at 03:05:57PM +0530, Aishwarya Narayanan wrote:
> Dear Git Organization,
> 
> I hope this email finds you well. I've prepared a patch to address an
> issue related to the handling of exit codes in our test suite
> concerning the Microproject idea Avoid suppressing Git’s exit code in
> test scripts. The changes ensure that the exit code of the write_utf16
> and write_utf32 functions is properly captured and not suppressed,
> improving the reliability of our testing process.
> I kindly request your review and any remarks or changes you may have.
> Please accept my apologies for any mistakes or oversights. Thank you
> for your time and attention.

Please not that patches are supposed to be sent as mails directly
instead of being attached to mails. You can use e.g. git-send-email(1)
to achieve this.

I would recommend to have a look "Documentation/MyFirstContribution.txt"
and "Documentation/SubmittingPatches". These resources should get you a
better picture of how a typical workflow would look like here.

Thanks!

Patrick

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-03-27  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27  9:35 GSoC 2024 [PATCH] Aishwarya Narayanan
2024-03-27  9:47 ` Patrick Steinhardt [this message]
2024-03-27 15:23   ` Junio C Hamano

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=ZgPrLXjB5mVXitXu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.