On Wed, 5 Feb 2014 13:39:47 -0800 (PST)
Philipp Kraus wrote:
> >> It is more a "social problem" and I don't want to fix encoding
> >> errors manually.
> >> Mostly user does not configurate their editors correct and I get
> >> after a commit
> >> encoding errors within the files, so I would like t
Am Mittwoch, 5. Februar 2014 21:55:30 UTC+1 schrieb Huu Da Tran:
>
> On Wednesday, February 5, 2014 9:59:30 AM UTC-5, Philipp Kraus wrote:
>>
>> It is more a "social problem" and I don't want to fix encoding errors
>> manually.
>> Mostly user does not configurate their editors correct and I get
On Wednesday, February 5, 2014 9:59:30 AM UTC-5, Philipp Kraus wrote:
>
> It is more a "social problem" and I don't want to fix encoding errors
> manually.
> Mostly user does not configurate their editors correct and I get after a
> commit
> encoding errors within the files, so I would like to co
Hello,
thanks for your answer.
Am Mittwoch, 5. Februar 2014 15:29:14 UTC+1 schrieb Konstantin Khomoutov:
Any sensible text editor
> these days supports it. It might require certain tweaking but writing
> a Git filter is way more pain in the neck.
>
It is more a "social problem" and I don't
On Wed, 5 Feb 2014 05:51:38 -0800 (PST)
Philipp Kraus wrote:
> can I use gitattributes for change the encoding of text file? I would
> like to encode all text file with UTF-8 and replace the \t to 4
> spaces. How can I do this?
Well, in theory, you can -- using the so-called "clean filter" (see
