{"thread":{"id":"7814","subject":"gitattributes","startedAt":"2007-04-24T11:36:56Z","lastAt":"2007-04-24T22:06:35Z","messageCount":5,"participants":["Matthias Kestenholz","Alex Riesen","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"40320","messageId":"1f6632e50704240436l4a81d8c9s1bbf95a7892db68c@mail.gmail.com","threadId":"7814","inReplyTo":null,"subject":"gitattributes","fromName":"Matthias Kestenholz","fromEmail":"lists@spinlock.ch","sentAt":"2007-04-24T11:36:56Z","receivedAt":"2007-04-24T11:36:56Z","isPatch":false,"sender":{"key":"lists@spinlock.ch","avatar":null},"body":"The .gitattributes system together with input/output filters has already\nproven exceptionally useful for me. I've got some co-workers which\ndo not seem to care about CRLF line endings or whitespace damage.\n\ncore.autocrlf = input\n\nand\n\n[filter \"whitespace\"]\n clean = stripspace\n smudge = cat\n\nand\n\n*.php filter=whitespace\n*.tpl filter=whitespace\n\nsaves me minutes every day when I review changes made by others,\nbecause otherwise the diffs are getting illegible (Sometimes, the whole\nfile is shown twice only because the line-ending changed)\n\nIt would be really great if these features were included in the next\nrelease.\n\n\nThanks,\nMatthias\n"},{"id":"40343","messageId":"81b0412b0704240918t70bfb3bt5f0e6e85028be5e6@mail.gmail.com","threadId":"7814","inReplyTo":"1f6632e50704240436l4a81d8c9s1bbf95a7892db68c@mail.gmail.com","subject":"Re: gitattributes","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-04-24T16:18:15Z","receivedAt":"2007-04-24T16:18:15Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"On 4/24/07, Matthias Kestenholz wrote:\n> The .gitattributes system together with input/output filters has already\n> proven exceptionally useful for me. I've got some co-workers which\n> do not seem to care about CRLF line endings or whitespace damage.\n>\n> core.autocrlf = input\n>\n> and\n>\n> [filter \"whitespace\"]\n> clean = stripspace\n> smudge = cat\n>\n\nWhy didn't --ignore-space-at-eol, -b and -w work for you?\n"},{"id":"40349","messageId":"7vy7kh66dn.fsf@assigned-by-dhcp.cox.net","threadId":"7814","inReplyTo":"1f6632e50704240436l4a81d8c9s1bbf95a7892db68c@mail.gmail.com","subject":"Re: gitattributes","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-04-24T17:15:32Z","receivedAt":"2007-04-24T17:15:32Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Matthias Kestenholz\" writes:\n\n> The .gitattributes system together with input/output filters has already\n> proven exceptionally useful for me. I've got some co-workers which\n> do not seem to care about CRLF line endings or whitespace damage.\n>\n> core.autocrlf = input\n>\n> and\n>\n> [filter \"whitespace\"]\n> clean = stripspace\n> smudge = cat\n\nYou shouldn't need to say \"smudge = cat\"; if it does not work\nwithout that line you found a bug, so please report.\n"},{"id":"40368","messageId":"7v4pn55u4d.fsf@assigned-by-dhcp.cox.net","threadId":"7814","inReplyTo":"81b0412b0704240918t70bfb3bt5f0e6e85028be5e6@mail.gmail.com","subject":"Re: gitattributes","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-04-24T21:40:18Z","receivedAt":"2007-04-24T21:40:18Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Alex Riesen\" writes:\n\n> On 4/24/07, Matthias Kestenholz wrote:\n>> The .gitattributes system together with input/output filters has already\n>> proven exceptionally useful for me. I've got some co-workers which\n>> do not seem to care about CRLF line endings or whitespace damage.\n>>\n>> core.autocrlf = input\n>>\n>> and\n>>\n>> [filter \"whitespace\"]\n>> clean = stripspace\n>> smudge = cat\n>>\n>\n> Why didn't --ignore-space-at-eol, -b and -w work for you?\n\nIt should. What Matthias would want more is probably to have\nothers to have the \"clean\" side of the filter in their working\nrepository.\n"},{"id":"40370","messageId":"1f6632e50704241506q15315ccbi239b5eee1f184b3e@mail.gmail.com","threadId":"7814","inReplyTo":"7v4pn55u4d.fsf@assigned-by-dhcp.cox.net","subject":"Re: gitattributes","fromName":"Matthias Kestenholz","fromEmail":"lists@spinlock.ch","sentAt":"2007-04-24T22:06:35Z","receivedAt":"2007-04-24T22:06:35Z","isPatch":false,"sender":{"key":"lists@spinlock.ch","avatar":null},"body":"2007/4/24, Junio C Hamano :\n> \"Alex Riesen\" writes:\n>\n> > On 4/24/07, Matthias Kestenholz wrote:\n> >> The .gitattributes system together with input/output filters has already\n> >> proven exceptionally useful for me. I've got some co-workers which\n> >> do not seem to care about CRLF line endings or whitespace damage.\n> >>\n> >> core.autocrlf = input\n> >>\n> >> and\n> >>\n> >> [filter \"whitespace\"]\n> >> clean = stripspace\n> >> smudge = cat\n> >>\n> >\n> > Why didn't --ignore-space-at-eol, -b and -w work for you?\n>\n> It should. What Matthias would want more is probably to have\n> others to have the \"clean\" side of the filter in their working\n> repository.\n\nYes, that's the reason. Furthermore, I like the approach of the filter\nbetter than adding command line arguments (which I and others will\nalways forget on the first try)\n\nI've just copy-pasted the smudge filter from an example I saw on\nthe list. I'll retest the filter setup tomorrow without \"smudge = cat\"\nand look for problems.\n"}]}