threads / discuss / 29534

filter-branch ignoring gitattributes?

Subject: filter-branch ignoring gitattributes?

## tl;dr

2 messages between Feb 3, 2012 and Feb 8, 2012.

replies: 1people: 1as markdown or json

norbert.nemec· Feb 3, 2012, 12:55 UTC · lore
Hi there,

it seems that 'git filter-branch' ignores the setting in .git/info/attributes - is that correct?

Does .gitattributes work reliably?
Specifically, I tried
	git filter-branch \
		--tree-filter 'echo "* text=auto" > .gitattributes' \
             	--tag-name-filter cat
		--prune-empty -- --all
It seems to work, but I am not sure whether I missed anything.

Greetings, Norbert

norbert.nemec· Feb 8, 2012, 08:23 UTC · re: norbert.nemec · lore

Re: filter-branch ignoring gitattributes?

Meanwhile, I can answer my own question:

The "text" attribute works similar to a filter. As with filters in general, it is only applied when git detects a modification in the file. A file change is detected by the file modification time on disc. To reread all files from disk and re-apply the filters to all of them, you would typically delete the .git/index file. In filter-branch, this is not possible, so instead you have to "touch" all files in the --tree-filter command.

Am 03.02.12 13:55, schrieb norbert.nemec:
Show 19 quoted lines
> Hi there,
>
> it seems that 'git filter-branch' ignores the setting in
> .git/info/attributes - is that correct?
>
> Does .gitattributes work reliably?
>
> Specifically, I tried
>
> git filter-branch \
> --tree-filter 'echo "* text=auto" > .gitattributes' \
> --tag-name-filter cat
> --prune-empty -- --all
>
> It seems to work, but I am not sure whether I missed anything.
>
> Greetings,
> Norbert
>

← back to recent threads