From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Francesco Paparatto <francescopaparatto@gmail.com>,
git@vger.kernel.org, Ayush Chandekar <ayu.chandekar@gmail.com>,
jltobler@gmail.com,
Siddharth Asthana <siddharthasthana31@gmail.com>,
karthik nayak <karthik.188@gmail.com>
Subject: Re: [GSoC Proposal] Refactoring in order to reduce Git's global state
Date: Sat, 21 Mar 2026 09:32:50 -0700 [thread overview]
Message-ID: <xmqq5x6pb0st.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD1H8ZsxfGSnnvX9xkKLSSpDjA3e3KNZ7eHN3ruq-sC7fw@mail.gmail.com> (Christian Couder's message of "Sat, 21 Mar 2026 14:36:01 +0100")
Christian Couder <christian.couder@gmail.com> writes:
>> * [GSoC PATCH v2] t3310: replace test -f/-d with
>> test_path_is_file/test_path_is_dir
>> Link: https://lore.kernel.org/git/20260228005939.9012-1-francescopaparatto@gmail.com/
>> Status: Graduated to 'master'.
>
> For commits which graduated to master, please give the commit ID of
> either the commits you authored or the merge commit that merged your
> commit(s) into master.
This might be way offtopic, I know, but the success criteria of
microproject being that the candidate has learned to effectively
communicate what they did and interact with others on the list,
it might be less work for both of you to drop "Status". Whether
the resulting commit is in my tree or not is of much lessor
importance than what we can see in the exchange in the discussion
thread.
next prev parent reply other threads:[~2026-03-21 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 17:54 [GSoC Proposal] Refactoring in order to reduce Git's global state Francesco Paparatto
2026-03-21 13:36 ` Christian Couder
2026-03-21 13:56 ` Francesco Paparatto
2026-03-21 16:32 ` Junio C Hamano [this message]
2026-03-24 19:31 ` [GSoC Proposal v2] " Francesco Paparatto
-- strict thread matches above, loose matches on Subject: below --
2026-03-06 14:57 [GSOC][PROPOSAL]: Refactoring in order to reduce Git’s " Shreyansh Paliwal
2026-03-07 10:33 ` Christian Couder
2026-03-07 12:46 ` Shreyansh Paliwal
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=xmqq5x6pb0st.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ayu.chandekar@gmail.com \
--cc=christian.couder@gmail.com \
--cc=francescopaparatto@gmail.com \
--cc=git@vger.kernel.org \
--cc=jltobler@gmail.com \
--cc=karthik.188@gmail.com \
--cc=siddharthasthana31@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