On 27/10/16 15:22, Stefan Beller wrote: >> The use case for this is where I did not write my own rules, but I want >> to keep them updated. https://github.com/github/gitignore is a damn good >> resource, but I want to pull it and include relevant bits project by >> project and/or system wide. I don't want to have to update many projects >> manually if that, or any other, repo changes. > > .git/info/exclude could be a (sym)link to an up to date version > of the gitignore repo as a hack? >
Using links isn't a bad idea, but you still end up at some stage combining the contents of several files that already exist. Well, in my example, anyway. I accept that I'm being pretty trivial, and once it's set up there's never any pressing need to change anything, but it still irks me. Even with a linked .gitignore, or .git/info/exclude there will be sections that are project, language, editor, machine, whatever, specific. So I still need to copy stuff from one file to another by hand. By allowing includes, I only have to have a link to each file describing the data types for each component of the environment. And they are community maintained, so I don't have to google every time I try a new editor. note to self: reply-to isn't the list.
