From: BILAL EL KHATABI <elkhatabibilal@gmail.com>
Cc: git@vger.kernel.org, pabloosabaterr@gmail.com, jltobler@gmail.com
Subject: Re: [GSOC PATCH v2] t5315: use test_path_is_file for loose-object check
Date: Thu, 19 Mar 2026 19:29:17 +0000 [thread overview]
Message-ID: <8669d87c1b7f96dd0de37dabfb9011c8745a17c9.camel@gmail.com> (raw)
In-Reply-To: <xmqqv7erk5oh.fsf@gitster.g>
Thanks, Junio and Pablo.
For the advice, will do.
I’ll also spend some time reading recent newcomer and GSoC-related
threads on lore before sending the next ones.
Best,
Bilal
next prev parent reply other threads:[~2026-03-19 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 16:02 [PATCH] t5315: use test_path_is_file for loose-object check Bilal El Khatabi
2026-03-19 16:26 ` Pablo
2026-03-19 18:35 ` Junio C Hamano
2026-03-19 18:06 ` [GSOC PATCH v2] " Bilal El Khatabi
2026-03-19 18:58 ` Junio C Hamano
2026-03-19 19:29 ` BILAL EL KHATABI [this message]
2026-03-20 10:08 ` Karthik Nayak
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=8669d87c1b7f96dd0de37dabfb9011c8745a17c9.camel@gmail.com \
--to=elkhatabibilal@gmail.com \
--cc=git@vger.kernel.org \
--cc=jltobler@gmail.com \
--cc=pabloosabaterr@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