From: shejialuo <shejialuo@gmail.com>
To: ps@pks.im
Cc: git@vger.kernel.org, gitster@pobox.com, karthik.188@gmail.com
Subject: Re: [GSoC][PROPOSAL v1] Implement consistency check for refs
Date: Tue, 26 Mar 2024 19:52:15 +0800 [thread overview]
Message-ID: <20240326115215.40180-1-shejialuo@gmail.com> (raw)
In-Reply-To: <ZgEwgNl3fug3qGG5@tanuki>
> Hum, okay. This does sound extremely taxing and I do wonder whether this
> is going to be a sustainable mode of working for multiple months in a
> row.
Such a long schedule might indeed be too intense, but I think it's very
flexible, and I can continue to improve this aspect of the work after
GSoC.
prev parent reply other threads:[~2024-03-26 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 10:03 [GSoC][PROPOSAL v1] Implement consistency check for refs shejialuo
2024-03-25 8:06 ` Patrick Steinhardt
2024-03-26 11:52 ` shejialuo [this message]
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=20240326115215.40180-1-shejialuo@gmail.com \
--to=shejialuo@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@gmail.com \
--cc=ps@pks.im \
/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).