Re: Why --backup-and-modify-in-place in perltidy config? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Why --backup-and-modify-in-place in perltidy config?
Date
Msg-id 2042.1471306913@sss.pgh.pa.us
Whole thread Raw
In response to Re: Why --backup-and-modify-in-place in perltidy config?  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Michael Paquier <michael.paquier@gmail.com> writes:
> The tree does not have any .bak file, and those refer to backup copies
> normally. Perhaps it would make sense to include those in root's
> .gitignore? That would save from an unfortunate manipulation of git
> add in the future.

We've generally refrained from adding things like that to the .gitignore
files.  If you've got unexpected trash in your tree, you probably ought
to be told about it.  There was some discussion back-when about including
common editor backup extensions and suchlike, but the consensus was that
those are better handled in user-private git config files.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PSA: Systemd will kill PostgreSQL
Next
From: Josh Berkus
Date:
Subject: Re: PSA: Systemd will kill PostgreSQL