git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Junio C Hamano <gitster@pobox.com>,
	Alexander Berntsen <alexander@plaimi.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] .gitignore: Ignore editor backup and swap files
Date: Thu, 16 Jan 2014 22:56:47 +0000	[thread overview]
Message-ID: <52D863AF.30506@ramsay1.demon.co.uk> (raw)
In-Reply-To: <xmqqtxd3y43b.fsf@gitster.dls.corp.google.com>

On 16/01/14 22:06, Junio C Hamano wrote:
> Alexander Berntsen <alexander@plaimi.net> writes:
> 
>> Signed-off-by: Alexander Berntsen <alexander@plaimi.net>
>> ---
>>  .gitignore | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/.gitignore b/.gitignore
>> index b5f9def..2905c21 100644
>> --- a/.gitignore
>> +++ b/.gitignore
>> @@ -240,3 +240,5 @@
>>  *.pdb
>>  /Debug/
>>  /Release/
>> +*~
>> +.*.swp
> 
> I personally do not mind listing these common ones too much, but if
> I am not mistaken, our policy on this file so far has been that it
> lists build artifacts, and not personal preference (the *.swp entry
> is useless for those who never use vim, for example).
> 
> These paths that depend on your choice of the editor and other tools
> can still be managed in your personal .git/info/exclude in the
> meantime.

As a vim user, I have these set in my ~/.gitignore file, which I refer
to from ~/.gitconfig using core.excludesfile. ;-)


ATB,
Ramsay Jones

  parent reply	other threads:[~2014-01-16 22:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 21:19 [PATCH] .gitignore: Ignore editor backup and swap files Alexander Berntsen
2014-01-16 22:06 ` Junio C Hamano
2014-01-16 22:15   ` Alexander Berntsen
2014-01-16 22:43   ` Jonathan Nieder
2014-01-17  6:20     ` Duy Nguyen
2014-01-16 22:56   ` Ramsay Jones [this message]
2014-01-17  4:48   ` David Kastrup

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=52D863AF.30506@ramsay1.demon.co.uk \
    --to=ramsay@ramsay1.demon.co.uk \
    --cc=alexander@plaimi.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).