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

Re: [RFC PATCH] fetch-pack: lazy fetch using tree:0

From
Jeff King <peff@peff.net>
Date
Mar 27, 2020, 09:37 UTC
Message-ID
<20200327093710.GA611304@coredump.intra.peff.net>
In-Reply-To
<20200326195058.GA8613@syl.local>
On Thu, Mar 26, 2020 at 01:50:58PM -0600, Taylor Blau wrote:
Show 9 quoted lines
> > One side note (for Taylor, cc'd): our patches elsewhere to limit the
> > allowed filters don't make it possible to express the difference between
> > "tree:0" and "tree:1". It may be worth thinking about that, especially
> > if it influences the config schema (since we'll have to support it
> > forever once it makes it into a release).
> [...]
>   [uploadpack "filter.tree:depth"]
>     allow = true
>     maxDepth = <n>

Yeah, that scheme solves the problem very neatly, and removes any worry I had about painting ourselves into a corner. Thanks.

-Peff
Previous: Taylor Blau
Message 5 of 5 in “fetch-pack: lazy fetch using tree:0”
  1. fetch-pack: lazy fetch using tree:0Jonathan Tan, Mar 19, 2020
  2. Derrick StoleeMar 19, 2020
  3. Jeff KingMar 20, 2020
  4. Taylor BlauMar 26, 2020
  5. Jeff KingMar 27, 2020

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.