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

RFC: Enable delayed responses to Git clean/smudge filter requests

From
Lars Schneider <larsxschneider@gmail.com>
Date
Nov 14, 2016, 21:09 UTC
Message-ID
<D10F7C47-14E8-465B-8B7A-A09A1B28A39F@gmail.com>
Hi,

Git always performs a clean/smudge filter on files in sequential order. Sometimes a filter operation can take a noticeable amount of time. This blocks the entire Git process.

I would like to give a filter process the possibility to answer Git with "I got your request, I am processing it, ask me for the result later!".

I see the following way to realize this:

In unpack-trees.c:check_updates() [1] we loop through the cache entries and "ask me later" could be an acceptable return value of the checkout_entry() call. The loop could run until all entries returned success or error.

The filter machinery is triggered in various other places in Git and all places that want to support "ask me later" would need to be patched accordingly.

--

Do you think this could be a viable approach? Do you see a better way?

Thanks, Lars

[1] https://github.com/git/git/blob/3ab228137f980ff72dbdf5064a877d07bec76df9/unpack-trees.c#L267
Next: Eric Wong
Message 1 of 16 in “RFC: Enable delayed responses to Git clean/smudge filter requests”
  1. Lars SchneiderNov 14, 2016
  2. Eric WongNov 15, 2016
  3. Lars SchneiderNov 15, 2016
  4. Junio C HamanoNov 15, 2016
  5. Lars SchneiderNov 16, 2016
  6. Junio C HamanoNov 16, 2016
  7. Lars SchneiderNov 16, 2016
  8. Junio C HamanoNov 16, 2016
  9. Jakub NarębskiNov 16, 2016
  10. Junio C HamanoNov 16, 2016
  11. Lars SchneiderNov 17, 2016
  12. Lars SchneiderNov 24, 2016
  13. Junio C HamanoNov 28, 2016
  14. Eric WongNov 15, 2016
  15. Stefan BellerJan 9, 2017
  16. Lars SchneiderJan 11, 2017

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.