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

Re: [PATCH 0/2] Avoiding errors when partial cloning a tagged blob

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 6, 2018, 22:18 UTC
Message-ID
<xmqqy3eogg98.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20180706212957.GD6195@aiede.svl.corp.google.com>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 8 quoted lines
> The upsides are that
> ...
> - down the line, it should make operations like "fetch just this one
>   tree" a little simpler, since you can use
>
>    filter blob:none
>    filter tree:none
>    want <this tree>
;-) 

I think this example, especially without the first line, would have a practical use, i.e. "grab the contents of this directory without recursing", and as such is a very convincing argument to support the approach taken by the solution presented here.

> ....  So I'm comfortable with the direction
> this series goes in, though I haven't looked at the patches in detail.
Likewise.  Thanks.
Previous: Jonathan NiederNext: Junio C Hamano
Message 8 of 12 in “Avoiding errors when partial cloning a tagged blob”
  1. 0/2 Avoiding errors when partial cloning a tagged blobJonathan Tan, Jul 6, 2018
  2. 1/2 upload-pack: send refs' objects despite "filter"Jonathan Tan, Jul 6, 2018
  3. 2/2 clone: check connectivity even if clone is partialJonathan Tan, Jul 6, 2018
  4. Jonathan TanJul 6, 2018
  5. Junio C HamanoJul 6, 2018
  6. Jonathan TanJul 6, 2018
  7. Jonathan NiederJul 6, 2018
  8. Junio C HamanoJul 6, 2018
  9. Junio C HamanoJul 9, 2018
  10. Jonathan TanJul 9, 2018
  11. Junio C HamanoJul 9, 2018
  12. Jonathan TanJul 9, 2018

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.