Re: .gitignore files, take two - Mailing list pgsql-hackers

From Tom Lane
Subject Re: .gitignore files, take two
Date
Msg-id 2735.1285081350@sss.pgh.pa.us
Whole thread Raw
In response to Re: .gitignore files, take two  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: .gitignore files, take two
Re: .gitignore files, take two
Re: .gitignore files, take two
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: .gitignore files, take two
Next
From: Robert Haas
Date:
Subject: Re: What happened to the is_ family of functions proposal?