From: "Ghanshyam Thakkar" <shyamthakkar001@gmail•com>
To: "Kaartic Sivaraam" <kaartic.sivaraam@gmail•com>,
"Patrick Steinhardt" <ps@pks•im>,
"Christian Couder" <christian.couder@gmail•com>
Cc: "Karthik Nayak" <karthik.188@gmail•com>,
"Jialuo She" <shejialuo@gmail•com>,
"Git Mailing List" <git@vger•kernel.org>,
"Junio C Hamano" <gitster@pobox•com>
Subject: Re: Git in GSoC 2025
Date: Sun, 16 Feb 2025 18:26:46 +0530 [thread overview]
Message-ID: <D7TVXVKVWRS8.S2BJN32QHZ0O@gmail.com> (raw)
In-Reply-To: <fa9ad3c6-3b3c-4f3c-89c6-101ed1b51eb6@gmail.com>
On Tue Feb 11, 2025 at 10:48 AM IST, Kaartic Sivaraam wrote:
> Hi Patrick, Christian and all,
>
> On 07/02/25 16:25, Patrick Steinhardt wrote:
> > One thought: From my point of view I'd strongly favor extending
> > git-refs(1) over reftable support in the dumb HTTP transport. So if I
> > had two applications, one for each topic, I'd lean towards applications
> > for the former topic. That might easily cause unfairness in case
> > students aren't aware of that.
> >
> > So unless somebody else wants to be main-mentor in that project, I think
> > we should either drop the HTTP transport tropic, or communicate our
> > priorities clearly.
>
> That makes sense. I've added a note to convey this clearly. Kindly check
> if the change in the following PR looks fine.
>
> https://github.com/git/git.github.io/pull/750/files
>
>
> On 07/02/25 13:37, Christian Couder wrote:
> > Yeah, but we have time to decide on this. It seems to me that we can
> > still come up with new project ideas and possibly new mentors or
> > co-mentors until it's time for applicants to send their.application.
>
> Indeed. More volunteer mentors and ideas are always welcome :-)
Hi,
I can co-mentor this summer. The 'Machine-Readable Repository Information
Query Tool' project seems interesting to me, although I'm up for co-mentoring
in other projects as well. Let me know if you need any help with
anything else.
Thanks.
next prev parent reply other threads:[~2025-02-16 12:56 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 10:13 Git in GSoC 2025 Kaartic Sivaraam
2025-01-20 7:07 ` Patrick Steinhardt
2025-01-20 13:38 ` shejialuo
2025-01-21 11:47 ` Oswald Buddenhagen
[not found] ` <CA+ARAtqfXo75PzzB3cQjDbvLxwytUK=xJiGG=VHZ1sNCcfyktQ@mail.gmail.com>
2025-01-27 8:06 ` Patrick Steinhardt
2025-01-27 12:43 ` shejialuo
2025-01-28 18:20 ` Kaartic Sivaraam
2025-01-28 17:30 ` Kaartic Sivaraam
2025-02-02 11:52 ` Kaartic Sivaraam
2025-02-03 8:45 ` Patrick Steinhardt
2025-02-03 11:53 ` Karthik Nayak
2025-02-04 2:29 ` shejialuo
2025-02-04 18:33 ` Kaartic Sivaraam
2025-02-05 13:20 ` Christian Couder
2025-02-07 7:32 ` Kaartic Sivaraam
2025-02-07 8:07 ` Christian Couder
2025-02-07 10:55 ` Patrick Steinhardt
2025-02-11 5:18 ` Kaartic Sivaraam
2025-02-16 12:56 ` Ghanshyam Thakkar [this message]
2025-02-16 13:53 ` Kaartic Sivaraam
2025-02-16 17:48 ` Junio C Hamano
2025-02-17 15:21 ` Ghanshyam Thakkar
2025-03-07 10:01 ` Karthik Nayak
2025-03-20 17:50 ` Kaartic Sivaraam
2025-03-21 21:02 ` Karthik Nayak
2025-02-08 15:34 ` shejialuo
2025-02-10 17:00 ` Karthik Nayak
2025-01-20 8:19 ` Christian Couder
2025-01-20 11:09 ` Patrick Steinhardt
2025-01-21 20:35 ` Junio C Hamano
2025-01-30 5:44 ` Kaartic Sivaraam
2025-01-30 7:32 ` Patrick Steinhardt
2025-01-30 8:37 ` Christian Couder
2025-01-30 10:56 ` Patrick Steinhardt
2025-01-30 19:18 ` Junio C Hamano
2025-01-30 21:00 ` Junio C Hamano
2025-01-31 4:51 ` Patrick Steinhardt
2025-01-31 16:09 ` Junio C Hamano
2025-02-03 8:49 ` Patrick Steinhardt
2025-01-31 4:48 ` Patrick Steinhardt
2025-02-03 13:21 ` Junio C Hamano
2025-02-04 18:36 ` Kaartic Sivaraam
2025-01-30 5:39 ` Kaartic Sivaraam
2025-01-20 10:12 ` Karthik Nayak
2025-01-20 13:27 ` shejialuo
2025-02-28 3:03 ` Kaartic Sivaraam
2025-02-28 5:06 ` shejialuo
2025-02-28 6:16 ` Patrick Steinhardt
2025-02-28 7:56 ` Christian Couder
2025-02-28 10:12 ` Ghanshyam Thakkar
2025-03-01 0:47 ` Kaartic Sivaraam
2025-03-03 10:00 ` 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=D7TVXVKVWRS8.S2BJN32QHZ0O@gmail.com \
--to=shyamthakkar001@gmail$(echo .)com \
--cc=christian.couder@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=kaartic.sivaraam@gmail$(echo .)com \
--cc=karthik.188@gmail$(echo .)com \
--cc=ps@pks$(echo .)im \
--cc=shejialuo@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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