| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why --backup-and-modify-in-place in perltidy config? |
| Date: | 2016-08-16 00:21:53 |
| Message-ID: | 2042.1471306913@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier <michael(dot)paquier(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2016-08-16 00:22:21 | Re: PSA: Systemd will kill PostgreSQL |
| Previous Message | Tom Lane | 2016-08-16 00:18:33 | Re: PSA: Systemd will kill PostgreSQL |