git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[GSoC] Discuss: Implement support for reftables in ‘dumb’ HTTP transport

From
Aryan Gupta <garyan447@gmail.com>
Date
Mar 13, 2024, 21:09 UTC
Message-ID
<CAMbn=B7MtohTm=J+XL8iwx_CuWo47jM-v=e=p+k6hY2CKWX+Og@mail.gmail.com>
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

Next: Junio C Hamano
Message 1 of 4 in “[GSoC] Discuss: Implement support for reftables in ‘dumb’ HTTP transport”
  1. Aryan GuptaMar 13, 2024
  2. Junio C HamanoMar 13, 2024
  3. Patrick SteinhardtMar 21, 2024
  4. Junio C HamanoMar 21, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.