From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: .gitignore files, take two |
Date: | 2010-09-21 15:02:30 |
Message-ID: | 2735.1285081350@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On tis, 2010-09-21 at 00:00 -0400, Tom Lane wrote:
>> 3. What are the ignore filesets *for*, in particular should they list
>> just the derived files expected in a distribution tarball, or all the
>> files in the set of build products in a normal build?
> My personal vote: Forget the whole thing.
The folks who are more familiar with git than I seem to be pretty clear
that we need to ignore all build products. I don't think that "ignore
nothing" is going to work pleasantly at all. On reflection I realize
that cvs ignore and git ignore are considerably different because they
come into play at different times: cvs ignore really only matters while
doing "cvs update" to pull in new code, while git ignore matters while
you're constructing a commit. So you really do need git ignore to
ignore all build products; otherwise you'll have lots of chatter in
"git status".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-09-21 15:03:28 | Re: What happened to the is_<type> family of functions proposal? |
Previous Message | Robert Haas | 2010-09-21 14:38:29 | Re: .gitignore files, take two |