Hi Elijah, On Sat, Feb 08, 2025 at 01:43:05PM -0800, Elijah Newren wrote: > Ooh, nice catch. If folks had an appropriate .gitattributes file in > place in older versions of history, they probably wouldn't have gotten > into the mess. Well, you can't assume that paople get it right from the very start. An important use case of git is fixing errors made in the past, right? In my case, I had no choice. I HAD to commit those propritary data files as-is, because I had no clue how they are structured and how those hashes are calculated. As time passed, I learned what I need to do to smudge+clean those files. But at that time a whole bunch of commits were already done. On this roadtrip, I had to modify those .gitattributes files in various ways. The only variant of those .gitattributes file which will work properly is the newest one. And this is also the variant wich will work for all the olter commits. So no, I don't see why using any of the older variants of this .gitattributes would make any sense. > ahah, so it is passed via environment variable to the subprocess. I find this to be confusing: the primary call should not need this parameter, since it is invoked from HEAD anyway. Everything else gets it via env-vars. I'd assume this variable will also be passed to the commands which are invoked by the -x switch? -- Josef Wolf jw@xxxxxxxxxxxxx
