git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Aryan Gupta <garyan447@gmail.com>
To: git@vger.kernel.org
Cc: karthik nayak <karthik.188@gmail.com>,
	"Patrick Steinhardt [ ]" <ps@pks.im>
Subject: [GSoC] Discuss: Implement support for reftables in ‘dumb’ HTTP transport
Date: Wed, 13 Mar 2024 22:09:59 +0100	[thread overview]
Message-ID: <CAMbn=B7MtohTm=J+XL8iwx_CuWo47jM-v=e=p+k6hY2CKWX+Og@mail.gmail.com> (raw)

Hello everyone.

I hope you are doing well. I am brainstorming on the problem
statement "Implement support for reftables in ‘dumb’ HTTP transport"
where I encountered some doubts which I wanted to discuss with you.

Problem statement link: https://git.github.io/SoC-2024-Ideas/ (Last one)

1. Do we just need support to know about the default branch or the
entire reftable?

2. As far as I am able to understand, I just need to add support for
these reftable files to transfer through the backend incase of dumb
http protocol, is this correct or am I missing something? In simple
words what I understand is I just need to add support for the server
side nothing is to be done for the client side.

I am sorry if these sound absolutely basic but I'm genuinely eager to
learn and implement them.

Thank you.

Regards
Aryan Gupta


             reply	other threads:[~2024-03-13 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 21:09 Aryan Gupta [this message]
2024-03-13 21:39 ` [GSoC] Discuss: Implement support for reftables in ‘dumb’ HTTP transport Junio C Hamano
2024-03-21 13:02   ` Patrick Steinhardt
2024-03-21 16:59     ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMbn=B7MtohTm=J+XL8iwx_CuWo47jM-v=e=p+k6hY2CKWX+Og@mail.gmail.com' \
    --to=garyan447@gmail.com \
    --cc=git@vger.kernel.org \
    --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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).