Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Sun, 17 Jun 2012 16:40:33 +0200
From: magnum <>
Subject: Re: .gitignore

On 2012-06-17 11:18, Frank Dittrich wrote:
> On 06/11/2012 07:41 PM, magnum wrote:
>> On 2012-06-11 12:26, Frank Dittrich wrote:
>>> BTW 1:
>>> Could you add
>>> *~
>>> *.patch
>>> to the .gitignore file of your repository?
>> Will do. Maybe *.diff too. I thought *~ was there already, maybe that's
>> in my .git/info/exclude (which doesn't replicate).
> May be *~ shouldn't even be in the central .gitignore.
> Someone who doesn't use any editor which creates *~ files wouldn't need
> this.
> So we could limit .gitignore to project specific exclusion patterns.
> Those who need this can add it to .git/info/exclude or a user specific
> global file.
> When I encountered a doc/.RULES.swp file
> $ file doc/.RULES.swp
> doc/.RULES.swp: Vim swap file, version 7.3
> I used
> $ git config --global core.excludesfile ~/.gitignore
> which added these lines to ~/.gitconfig
> [core]
> 	excludesfile = /home/fd/.gitignore
> (If you want to track your home directory with git, you might want to
> pick another excludesfile name, and use ~/.gitignore just for your home
> directory.)
> Then, I added this line to my ~./gitignore file:
> .*.sw?

For your swap file I agree but *~ is so common I think it can be in the 
shared .gitignore. On the other hand I don't care too much - I had 
everything in .git/info/exclude until Dhiru added .gitignore.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.