{"thread":{"id":"23552","subject":"No way to have global diff settings? (global .gitattributes feature request)","startedAt":"2010-04-21T17:05:53Z","lastAt":"2010-04-26T14:48:53Z","messageCount":4,"participants":["Štěpán Němec","Matthieu Moy","Michael J Gruber"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"140044","messageId":"87zl0wd9ce.fsf@gmail.com","threadId":"23552","inReplyTo":null,"subject":"No way to have global diff settings? (global .gitattributes feature request)","fromName":"Štěpán Němec","fromEmail":"stepnem@gmail.com","sentAt":"2010-04-21T17:05:53Z","receivedAt":"2010-04-21T17:05:53Z","isPatch":false,"sender":{"key":"stepnem@gmail.com","avatar":"https://avatars.githubusercontent.com/u/106838?v=4"},"body":"\nHello,\n\nit seems there is no global .gitattribute equivalent to .gitignore or\n.gitconfig. Wouldn't it make much sense to have one? Failing that, there\nreally should be a way to specify some global diff options at least.\n\nMy use case:\n\nI wanted to specify something like -F \"^(\" to git diff for lisp files.\nBut well, git diff has no -F option! So shruggar from #git pointed me to\ngitattributes. OK, that's great and works, but now I have to put\n.gitattributes or info/attributes to all repos with lisp files in them?\nThat rather sucks, if you ask me.\n\nSo I would like to ask if there is a way, and if not, if it could be\nconsidered a useful feature addition.\n\nThanks,\n\n  Štěpán\n"},{"id":"140414","messageId":"87och6ib0r.fsf@gmail.com","threadId":"23552","inReplyTo":"87zl0wd9ce.fsf@gmail.com","subject":"Re: No way to have global diff settings? (global .gitattributes feature request)","fromName":"Štěpán Němec","fromEmail":"stepnem@gmail.com","sentAt":"2010-04-26T13:44:20Z","receivedAt":"2010-04-26T13:44:20Z","isPatch":false,"sender":{"key":"stepnem@gmail.com","avatar":"https://avatars.githubusercontent.com/u/106838?v=4"},"body":"Štěpán Němec <stepnem@gmail.com> writes:\n\n> Hello,\n>\n> it seems there is no global .gitattribute equivalent to .gitignore or\n> .gitconfig. Wouldn't it make much sense to have one? Failing that, there\n> really should be a way to specify some global diff options at least.\n>\n> My use case:\n>\n> I wanted to specify something like -F \"^(\" to git diff for lisp files.\n> But well, git diff has no -F option! So shruggar from #git pointed me to\n> gitattributes. OK, that's great and works, but now I have to put\n> .gitattributes or info/attributes to all repos with lisp files in them?\n> That rather sucks, if you ask me.\n>\n> So I would like to ask if there is a way, and if not, if it could be\n> considered a useful feature addition.\n>\n> Thanks,\n>\n>   Štěpán\n\nPING\n"},{"id":"140415","messageId":"vpqoch6fhoz.fsf@bauges.imag.fr","threadId":"23552","inReplyTo":"87och6ib0r.fsf@gmail.com","subject":"Re: No way to have global diff settings? (global .gitattributes feature request)","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2010-04-26T13:48:28Z","receivedAt":"2010-04-26T13:48:28Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Štěpán Němec <stepnem@gmail.com> writes:\n\n>> Hello,\n>>\n>> it seems there is no global .gitattribute equivalent to .gitignore or\n>> .gitconfig. Wouldn't it make much sense to have one? Failing that, there\n>> really should be a way to specify some global diff options at least.\n\nI'd like this feature too. My use-case is to have antiword and odt2txt\nas textconv filters for .doc and .odt files, which I always want to\ndo. But probably the feature won't get implemented until one of us\nwrites a patch ;-) (I may have time later, but not before a few\ndays/weeks).\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"140419","messageId":"4BD5A7D5.3060203@drmicha.warpmail.net","threadId":"23552","inReplyTo":"vpqoch6fhoz.fsf@bauges.imag.fr","subject":"Re: No way to have global diff settings? (global .gitattributes feature request)","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2010-04-26T14:48:53Z","receivedAt":"2010-04-26T14:48:53Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Matthieu Moy venit, vidit, dixit 26.04.2010 15:48:\n> Štěpán Němec <stepnem@gmail.com> writes:\n> \n>>> Hello,\n>>>\n>>> it seems there is no global .gitattribute equivalent to .gitignore or\n>>> .gitconfig. Wouldn't it make much sense to have one? Failing that, there\n>>> really should be a way to specify some global diff options at least.\n> \n> I'd like this feature too. My use-case is to have antiword and odt2txt\n> as textconv filters for .doc and .odt files, which I always want to\n> do. But probably the feature won't get implemented until one of us\n> writes a patch ;-) (I may have time later, but not before a few\n> days/weeks).\n\nI leave it up to you to do the (re)search, but there's some preexisting\npatches and discussion around this topic. The upshot is that currently:\n\nSYSTEM                  | GLOBAL             | VERSIONED             | LOCAL\n\n$(prefix)/etc/gitconfig | $(HOME)/.gitconfig | N/A                   |\n$(GIT_DIR)/config\n\nN/A                     | N/A                | .gitattributes (rec.) |\n$GIT_DIR/info/attributes\n\nN/A                     | N/A                | .gitignore (rec.)     |\n$GIT_DIR/info/exclude\n\nThere's also GIT_CONFIG overriding the defaults, and core.exludesfiles\n(yes, with s!); and of course command line parameters.\n\nThere's been requests for versioned config, for multiple sources of\nsystem config (think config.d/*), for global and system versions of\nattributes and exclude/ignore, for saner naming of exclude(s) vs.\nignore, and, finally, for stopping all this madness, or rather: putting\nall of it in a subdir, aptly named gitconfig... no-no, no-go... or\nfollowing the XDG conventions, or...\n\nSo, you see: You may suggest something simple like core.attributesfile.\nI have a prediction how that goes.\n\nBut now, right after 1.7.1, it might be a good time to really settle\nthis in a future-proof yet backwards-compatible way.\n\nMichael\n"}]}