Re: gitattributes

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: gitattributes

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:06

"Alex Riesen" [off-list ref] writes:
On 4/24/07, Matthias Kestenholz [off-list ref] wrote:
quoted
The .gitattributes system together with input/output filters has already
proven exceptionally useful for me. I've got some co-workers which
do not seem to care about CRLF line endings or whitespace damage.

core.autocrlf = input

and

[filter "whitespace"]
  clean = stripspace
  smudge = cat
Why didn't --ignore-space-at-eol, -b and -w work for you?
It should.  What Matthias would want more is probably to have
others to have the "clean" side of the filter in their working
repository.

Re: gitattributes

From: Matthias Kestenholz <hidden>
Date: 2016-06-15 22:43:06

2007/4/24, Junio C Hamano [off-list ref]:
"Alex Riesen" [off-list ref] writes:
quoted
On 4/24/07, Matthias Kestenholz [off-list ref] wrote:
quoted
The .gitattributes system together with input/output filters has already
proven exceptionally useful for me. I've got some co-workers which
do not seem to care about CRLF line endings or whitespace damage.

core.autocrlf = input

and

[filter "whitespace"]
  clean = stripspace
  smudge = cat
Why didn't --ignore-space-at-eol, -b and -w work for you?
It should.  What Matthias would want more is probably to have
others to have the "clean" side of the filter in their working
repository.
Yes, that's the reason. Furthermore, I like the approach of the filter
better than adding command line arguments (which I and others will
always forget on the first try)

I've just copy-pasted the smudge filter from an example I saw on
the list. I'll retest the filter setup tomorrow without "smudge = cat"
and look for problems.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help