Le 24/09/2010 10:36, Magnus Hagander a écrit : > On Fri, Sep 24, 2010 at 10:34, Guillaume Lelarge <guilla...@lelarge.info> > wrote: >> Le 24/09/2010 10:23, Magnus Hagander a écrit : >>> On Fri, Sep 24, 2010 at 10:17, Guillaume Lelarge <guilla...@lelarge.info> >>> wrote: >>>> I was reading pgsql-hackers this morning while waiting for my >>>> colleagues. There's an interesting thread on gitignore files. Right now, >>>> when you grab a git branch, bootstrap it, configure it and make it, "git >>>> status" shows a lot of uninteresting files. A .gitignore file would help >>>> to notice changed files. I've come with the file attached, but would >>>> like to get comments on this. >>> >>> Haven't looked at the contents of the file, but definitely +1 on the >>> concept in genereal (probably not surprising, since I did the same >>> thing for the postgresql repo :P) >>> >> >> Yeah, I took a look at the mail where you show all the changes done, and >> I worked from this. I have one question about it. There is many >> .gitignore files. Why not a single one? what are the advantages of the >> multi-file way? > > That you'll always find the local targets in the directory you're > currently working, and when you need to add a new one, you do it next > to the file where it was done. >
OK, should we do that? It would be really easy to do. > That was actually discussed in the thread on -hackers :P > Didn't remember that. -- Guillaume http://www.postgresql.fr http://dalibo.com -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
