git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Luma <ach.lumap@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [Outreachy] Move existing tests to a unit testing framework
Date: Tue, 03 Oct 2023 11:51:34 -0700	[thread overview]
Message-ID: <xmqqedibzgi1.fsf@gitster.g> (raw)
In-Reply-To: <CAFR+8DynAJ7eieMYUrezoNii5tzARNbESFxRCcT4w6okS5FZDg@mail.gmail.com> (Luma's message of "Tue, 3 Oct 2023 15:30:18 +0100")

Luma <ach.lumap@gmail.com> writes:

> Hi;
> My name is Luma, and  I wanted to take a moment to introduce myself
> and share some
> insights on an essential aspect of  avoiding pipes in git related
> commands in test scripts.
>
> I am an outreachy applicant for the December 2023 cohort and look
> forward to learning from you.

I notice that the title of the message and the immediate topic you
discuss in the body of the message do not match.  I presume that the
topic on the title is what you prefer to work on if the unit testing
framework is ready by the time Outreachy program starts, and the
mention about "do not clobber exit code of Git with pipes in the
tests" is your "dip the tip of a toe in water" microproject?

Welcome to the Git development community.

Do you have a single word name?  If so please disregard the below,
but in case "Luma" is just a nickname (e.g. like I am introducing
myself to my Git friends "Hi, I am Gitster!") you use online, please
read on.

For signing off your patches, we'd prefer to see your real name
used, as Signed-off-by: is meant to have legal significance.  And
because we also expect the authorship identity to match the
name/e-mail of the sign-off, it would mean your patch submissions
are expected to look like:

	From: Luma <ach.lumap@gmail.com>
	Subject: ... title of the patch goes here ...

	... body of the proposed commit log message goes here...

	Signed-off-by: Luma <ach.lumap@gmail.com>

but "Luma" replaced with your full real name.

Thanks.

  reply	other threads:[~2023-10-03 18:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 14:30 [Outreachy] Move existing tests to a unit testing framework Luma
2023-10-03 18:51 ` Junio C Hamano [this message]
2023-10-03 23:36   ` Luma
2023-10-09  9:15     ` Luma
     [not found]       ` <CAFR+8Dwxr3iV+R7een0t2sYXUWu1XHhQcLVuqMhOsSg9Bt4wrg@mail.gmail.com>
2023-10-20 13:18         ` Achu Luma
2023-10-23 13:41         ` Christian Couder
2023-10-24 14:25           ` Achu Luma
2023-10-25  8:18             ` 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=xmqqedibzgi1.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ach.lumap@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).