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

Re: [PATCH] [RFC] list-objects-filter: introduce new filter sparse:buffer=<spec>

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 8, 2022, 16:15 UTC
Message-ID
<xmqqczdau2yd.fsf@gitster.g>
In-Reply-To
<pull.1316.git.1659958159193.gitgitgadget@gmail.com>
"ZheNing Hu via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 7 quoted lines
> From: ZheNing Hu <adlternative@gmail.com>
>
> Although we already had a `--filter=sparse:oid=<oid>` which
> can used to clone a repository with limited objects which meet
> filter rules in the file corresponding to the <oid> on the git
> server. But it can only read filter rules which have been record
> in the git server before.

Was the reason why we have "we limit to an object we already have" restriction because we didn't want to blindly use a piece of uncontrolled arbigrary end-user data here? Just wondering.

Previous: ZheNing Hu via GitGitGadgetNext: ZheNing Hu
Message 2 of 9 in “[RFC] list-objects-filter: introduce new filter sparse:buffer=<spec>”
  1. [RFC] list-objects-filter: introduce new filter sparse:buffer=<spec>ZheNing Hu via GitGitGadget, Aug 8, 2022
  2. Junio C HamanoAug 8, 2022
  3. ZheNing HuAug 9, 2022
  4. Derrick StoleeAug 9, 2022
  5. Jeff KingAug 10, 2022
  6. ZheNing HuAug 12, 2022
  7. Jeff KingAug 14, 2022
  8. ZheNing HuAug 12, 2022
  9. ZheNing HuAug 26, 2022

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.