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

From Tom Lane
Subject Re: .gitignore files, take two
Date
Msg-id 3332.1285082858@sss.pgh.pa.us
Whole thread Raw
In response to Re: .gitignore files, take two  (Magnus Hagander <magnus@hagander.net>)
Responses Re: .gitignore files, take two
Re: .gitignore files, take two
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> Breaking it up was quite trivial. Here's what I came up with after
> building on my box. I'm sure there are some on other platforms showing
> up, but this should be the majority.

> I just realized it does not include contrib, but's that a mechanical
> copy of the same thing.

> So if we want to go with this way, i have the scripts/changes ready :)

This works for me, modulo some things:

If we are going to ignore *.so at the top level, we also need to ignore
*.sl (for HPUX) and *.dll (for Windows).  I also wonder why we have
entries like this:

> +libecpg.a
> +libecpg.so.*

rather than global ignore patterns for *.a and *.so.[0-9]

We should probably ignore src/Makefile.custom, since that is still a
supported way to customize builds (and some of us still use it).

> diff --git a/src/timezone/.gitignore b/src/timezone/.gitignore
> new file mode 100644
> index 0000000..f844c9f
> --- /dev/null
> +++ b/src/timezone/.gitignore
> @@ -0,0 +1 @@
> +/zic

Why does this entry have a / when none of the rest do?  Shouldn't
we be consistent about that?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Configuring synchronous replication
Next
From: "Kevin Grittner"
Date:
Subject: moving development branch activity to new git repo