| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Copypasta in the PostgreSQL source |
| Date: | 2018-12-17 17:35:55 |
| Message-ID: | 20181217173554.GC416@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Folks,
Please find attached a run of a tool that looks for duplicated tokens.
I've removed some things that seem like false positives, basically all
from the stemmer part of the source, but there's still a lot.
- Is it worth trying to track these down and factor them out?
- Would it make sense to make some kind of git commit trigger that at
least warns when a new one has been introduced?
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
| Attachment | Content-Type | Size |
|---|---|---|
| copypasta.txt.gz | application/gzip | 141.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2018-12-17 17:45:53 | Re: Referential Integrity Checks with Statement-level Triggers |
| Previous Message | Alvaro Herrera | 2018-12-17 17:27:29 | Re: Referential Integrity Checks with Statement-level Triggers |