Re: [HACKERS] Ignoring entries generated by autoconf in code tree

2015-03-30 Thread Tom Lane
Peter Eisentraut writes: > On 3/25/15 10:34 AM, Tom Lane wrote: >> Michael Paquier writes: >>> When running autoconf from the root tree, autom4te.cache/ is >>> automatically generated. >>> Wouldn't it make sense to add an entry in .gitignore for that? >> Personally, I don't want such a thing, as

Re: [HACKERS] Ignoring entries generated by autoconf in code tree

2015-03-30 Thread Peter Eisentraut
On 3/25/15 10:34 AM, Tom Lane wrote: > Michael Paquier writes: >> When running autoconf from the root tree, autom4te.cache/ is >> automatically generated. >> Wouldn't it make sense to add an entry in .gitignore for that? > > Personally, I don't want such a thing, as then I would tend to forget >

Re: [HACKERS] Ignoring entries generated by autoconf in code tree

2015-03-25 Thread Tom Lane
Michael Paquier writes: > When running autoconf from the root tree, autom4te.cache/ is > automatically generated. > Wouldn't it make sense to add an entry in .gitignore for that? Personally, I don't want such a thing, as then I would tend to forget to remove that cache file. And you do want to r

[HACKERS] Ignoring entries generated by autoconf in code tree

2015-03-25 Thread Michael Paquier
Hi all, When running autoconf from the root tree, autom4te.cache/ is automatically generated. Wouldn't it make sense to add an entry in .gitignore for that? Regards, -- Michael diff --git a/.gitignore b/.gitignore index 8d3af50..b1f04bb 100644 --- a/.gitignore +++ b/.gitignore @@ -28,6 +28,7 @@ l