From: Aaron Pelly <aaron@pelly.co>
To: unlisted-recipients:; (no To-header on input)
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Expanding Includes in .gitignore
Date: Thu, 27 Oct 2016 22:51:38 +1300 [thread overview]
Message-ID: <0cf156b2-8fc1-2eb7-e26c-f11f59eec4e2@pelly.co> (raw)
In-Reply-To: <CAGZ79kasr6ubuOm01rLtdK7pfWqriZE1vioLyxAr2G2Hd1xGhg@mail.gmail.com>
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.
next prev parent reply other threads:[~2016-10-27 14:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 0:22 Expanding Includes in .gitignore Aaron Pelly
2016-10-27 2:22 ` Stefan Beller
2016-10-27 9:51 ` Aaron Pelly [this message]
2016-10-27 8:19 ` Alexei Lozovsky
2016-10-27 10:33 ` Aaron Pelly
2016-10-27 10:50 ` Jeff King
2016-10-27 19:48 ` Jacob Keller
2016-10-27 20:59 ` Aaron Pelly
2016-10-27 21:04 ` Jeff King
2016-10-27 21:26 ` Aaron Pelly
2016-10-27 21:39 ` Jacob Keller
2016-10-30 3:09 ` Duy Nguyen
2016-10-27 20:28 ` Aaron Pelly
2016-10-27 20:55 ` Jeff King
2016-10-27 21:07 ` Jeff King
2016-10-27 22:30 ` Aaron Pelly
2016-10-27 23:07 ` Aaron Pelly
2016-10-28 2:54 ` Junio C Hamano
2016-10-28 9:32 ` Aaron Pelly
2016-10-30 3:16 ` Duy Nguyen
2016-10-30 12:54 ` Jeff King
2016-10-27 21:55 ` Aaron Pelly
2016-10-27 22:17 ` Aaron Pelly
2016-10-28 8:10 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0cf156b2-8fc1-2eb7-e26c-f11f59eec4e2@pelly.co \
--to=aaron@pelly.co \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).