From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Lars Vogel <lars.vogel@gmail.com>,
git@vger.kernel.org, Lars Vogel <Lars.Vogel@vogella.com>
Subject: Re: [PATCH] Adds *~ to the .gitignore
Date: Thu, 09 Jun 2016 15:48:12 -0700 [thread overview]
Message-ID: <xmqqd1nqges3.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160609213809.GA23059@sigill.intra.peff.net> (Jeff King's message of "Thu, 9 Jun 2016 17:38:09 -0400")
Jeff King <peff@peff.net> writes:
> On Thu, Jun 09, 2016 at 02:21:55PM -0700, Junio C Hamano wrote:
>
>> Lars Vogel <lars.vogel@gmail.com> writes:
>>
>> > This helps contributors (like me) using editors which automatically create ~ copies of the changed data
>> >
>> > Signed-off-by: Lars Vogel <Lars.Vogel@vogella.com>
>> > ---
>>
>> We deliberately left this out and kept it out of .gitignore for the
>> past 10 years. The justification was that use of Emacs is merely a
>> personal choice that is better served by .git/info/excludes; we do
>> not add .swp for vim users, either, for the same reason.
>
> I think a better choice than .git/info/excludes these days is
> ~/.config/git/ignore. Then it is associated with the user, not the
> project (which seems a better fit, since it is the user who is picking
> the editor; this should apply across all projects).
Yes, that is a better alternative you can use these days, of course.
Thanks.
As I said, however, I could support a move to add some selected
small number of common file extensions, as long as we have some
(social) mechanism to avoid churning this file every time somebody
new comes and complains their favourite editor or other tools are
not supported.
next prev parent reply other threads:[~2016-06-09 22:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 21:10 [PATCH] Adds *~ to the .gitignore Lars Vogel
2016-06-09 21:21 ` Junio C Hamano
2016-06-09 21:38 ` Jeff King
2016-06-09 22:48 ` Junio C Hamano [this message]
2016-06-09 23:31 ` Jeff King
2016-06-10 15:52 ` Junio C Hamano
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=xmqqd1nqges3.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Lars.Vogel@vogella.com \
--cc=git@vger.kernel.org \
--cc=lars.vogel@gmail.com \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.