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

Re: Some issues when trying to set up a shallow git mirror server

From
Richard Maw <richard.maw@codethink.co.uk>
Date
Jan 13, 2016, 17:43 UTC
Message-ID
<20160113174331.GI3397@logi.codethink.co.uk>
In-Reply-To
<xmqqlh7tpfkt.fsf@gitster.mtv.corp.google.com>
On Wed, Jan 13, 2016 at 09:14:10AM -0800, Junio C Hamano wrote:
Show 15 quoted lines
> Richard Maw <richard.maw@codethink.co.uk> writes:
> 
> > 1.  Before any "want" requests.
> >
> >     This would also let you extend ls-remote to let it display ancestry.
> >
> >     This is complicated by the fact that normally the client responds
> >     with which features it supports in the first "want",
> >     so the sender would have to support "check-ff N O <FEATURES>"
> >     if it advertised "ancestry-check".
> 
> Yes, that sounds like a good thing.  Actually, ls-remote is a
> degenerated case of fetch that sends 0 "want" requests, so the above
> may be identical to what I suggested in the message you are
> responding to.
Thanks. I've got a good idea of what I'd need to do now.
Previous: Junio C Hamano
Message 11 of 11 in “Some issues when trying to set up a shallow git mirror server”
  1. Richard MawJan 7, 2016
  2. Junio C HamanoJan 7, 2016
  3. Richard MawJan 8, 2016
  4. Duy NguyenJan 8, 2016
  5. Richard MawJan 8, 2016
  6. Junio C HamanoJan 8, 2016
  7. Richard MawJan 11, 2016
  8. Junio C HamanoJan 12, 2016
  9. Richard MawJan 13, 2016
  10. Junio C HamanoJan 13, 2016
  11. Richard MawJan 13, 2016

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.