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

[Best Practices Request] clean/smudge configuration

From
Randall S. Becker <rsbecker@nexbridge.com>
Date
May 9, 2018, 22:08 UTC
Message-ID
<004d01d3e7e2$517f78d0$f47e6a70$@nexbridge.com>
Hi Git Team,

I'm trying to work out some best practices for managing clean/smudge filters and hit a bump. The situation is that I have an environment where the possible clean/smudge filter configuration can change over time and needs to be versioned with the product being managed in a git repository. Part of the configuration is no problem in .gitattributes, but the other bits are in .git/config. I get that the runnable part of the filters need to be strictly platform independent in principle, but I can abstract that part in this situation.

The question: what is the best practice for versioning the parts of clean/smudge filters that are in .git/config given that only some users in my environment will be cloning the repository in question and that I really can't put the entries in /etc/gitconfig or ~/.gitconfig because of potential conflicts with other repositories that might also have clean/smudge definitions.

Thanks, Randall

Next: Bryan Turner
Message 1 of 6 in “[Best Practices Request] clean/smudge configuration”
  1. Randall S. BeckerMay 9, 2018
  2. Bryan TurnerMay 9, 2018
  3. Randall S. BeckerMay 9, 2018
  4. Randall S. BeckerMay 10, 2018
  5. Junio C HamanoMay 11, 2018
  6. Randall S. BeckerMay 11, 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.