From: Patrick Steinhardt <ps@pks.im>
To: Aryan Gupta <garyan447@gmail.com>
Cc: git@vger.kernel.org, karthik nayak <karthik.188@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [GSoC][PROPOSAL v1] Refactor git-bisect(1) to make its state self-contained
Date: Thu, 21 Mar 2024 15:39:35 +0100 [thread overview]
Message-ID: <ZfxGp6p6RiS5i5SD@tanuki> (raw)
In-Reply-To: <CAMbn=B73ioQ8oRucG4X8anhwrnbhJRky7BSe7DKpQad85Dt5xg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
On Thu, Mar 21, 2024 at 02:27:56PM +0100, Aryan Gupta wrote:
> On Thu, Mar 21, 2024 at 1:48 PM Patrick Steinhardt <ps@pks.im> wrote:
[snip]
> > If you want to stick with this idea then I would strongly recommend that
> > you mention this in your proposal.
> >
> I am open to changing to another idea, I won't mind that. Because my
> ultimate aim to add something (even it's a small patch) to git and if
> this project will never be in use. I am willing to change it. Let me know
> what you think about it.
I'll leave it up to you to pick the project you're most interested in. I
only want to ensure that you have as much information as required to do
a proper assessment of the different proposed projects. So if you want
to stick to the idea then that's fine. If you want to switch now, then
that is fine, too.
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-03-21 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 18:57 [GSoC][PROPOSAL v1] Refactor git-bisect(1) to make its state self-contained Aryan Gupta
2024-03-20 11:06 ` Christian Couder
2024-03-21 13:21 ` Aryan Gupta
2024-03-26 10:29 ` Christian Couder
2024-03-27 0:23 ` Aryan Gupta
2024-03-23 16:37 ` Aryan Gupta
2024-03-21 12:48 ` Patrick Steinhardt
2024-03-21 13:27 ` Aryan Gupta
2024-03-21 14:39 ` Patrick Steinhardt [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=ZfxGp6p6RiS5i5SD@tanuki \
--to=ps@pks.im \
--cc=christian.couder@gmail.com \
--cc=garyan447@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@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;
as well as URLs for NNTP newsgroup(s).