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

Re: proposal for extending smudge/clean filters with raw file access

From
Joey Hess <id@joeyh.name>
Date
May 12, 2016, 21:02 UTC
Message-ID
<20160512210227.GA10786@kitenet.net>
In-Reply-To
<xmqqvb2jf6dg.fsf@gitster.mtv.corp.google.com>
Junio C Hamano wrote:
Show 6 quoted lines
> The smudge happens to be the last to run, so it is quite true that
> it can say "Hey Git, I've written it out already".
> 
> I didn't check all codepaths to ensure that we won't need the
> smudged result in core at all, but I am guessing you did so before
> making this proposal, so in that case I would say this sounds fine.

Well, the idea is to only use smudge-to-file when the smudged content is going to be written out to a file. Any other code paths that need to smudge some content would use the smudge filter.

So, try_create_file would use it. Maybe some other places I have not found yet could as well.

-- 
see shy jo
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 7 in “proposal for extending smudge/clean filters with raw file access”
  1. Joey HessMay 12, 2016
  2. Junio C HamanoMay 12, 2016
  3. Joey HessMay 12, 2016
  4. Junio C HamanoMay 12, 2016
  5. Joey HessMay 12, 2016
  6. Junio C HamanoMay 12, 2016
  7. Joey HessMay 12, 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.