Git development
 help / color / mirror / Atom feed
From: Ogundipe Sola Taiwo <ogundipesolataiwo12@gmail.com>
To: Usman Akinyemi <usmanakinyemi202@gmail.com>
Cc: Ogundipe Sola Taiwo <ogundipesolataiwo12@gmail.com>,
	Christian Couder <christian.couder@gmail.com>,
	Siddharth Asthana <siddharthasthana31@gmail.com>,
	git@vger.kernel.org
Subject: [Outreachy] Microproject: Modernize file check in t5300-pack-object.sh
Date: Tue, 27 Oct 2026 14:42:43 -0400	[thread overview]
Message-ID: <20261027184342.3948-1-ogundipesolataiwo12@gmail.com> (raw)
In-Reply-To: <20261023154851.7876-1-ogundipesolataiwo12@gmail.com>

> Could you rephrase this to avoid “This commit”? It's redundant in a
> commit message."
> Please describe the change directly instead. Also, I believe, the term
> patch is more
> appropriate and not "commit".

Thanks for catching that. I've rephrased it.

  parent reply	other threads:[~2026-10-27 18:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 15:48 [Outreachy] Microproject: Modernize file check in t5300-pack-object.sh Ogundipe Sola Taiwo
2026-10-26 10:20 ` [PATCH] t5300: modernize test path checks in t5300 Ogundipe Sola Taiwo
2026-10-27 16:56   ` Usman Akinyemi
2026-10-26 20:32 ` [Outreachy] Microproject: Modernize file check in t5300-pack-object.sh Usman Akinyemi
2026-10-27 18:36 ` [PATCH v2] t5300: modernize test path checks in t5300 Ogundipe Sola Taiwo
2026-10-28 14:02   ` Usman Akinyemi
2026-10-28 14:12   ` Junio C Hamano
2026-10-27 18:42 ` Ogundipe Sola Taiwo [this message]
2026-10-29 11:48 ` [Outreachy] Microproject: Modernize file check in t5300-pack-object.sh Ogundipe Sola Taiwo
2026-10-29 12:02 ` [PATCH v3] t5300: modernize test path checks in t5300 Ogundipe Sola Taiwo
2026-10-29 18:36   ` 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=20261027184342.3948-1-ogundipesolataiwo12@gmail.com \
    --to=ogundipesolataiwo12@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=siddharthasthana31@gmail.com \
    --cc=usmanakinyemi202@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