| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: rename sgml files? |
| Date: | 2018-02-16 20:47:21 |
| Message-ID: | 26291.1518814041@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> On 2/12/18 16:19, Tom Lane wrote:
>> At that point, back-patching documentation fixes would become effectively
>> impossible except through manual intervention in the patching process.
> Are you not using git cherry-pick?
Yes, when it works, which it tends not to in cases that are even a little
bit complicated. I have zero faith that it works across a file rename,
and would not like to give up the option of using patch(1) instead. (See,
eg, recent discussions about the fragility of "git apply" vs "patch".)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brian Cloutier | 2018-02-16 20:57:40 | Re: Add PGDLLIMPORT to enable_hashagg |
| Previous Message | Peter Eisentraut | 2018-02-16 20:32:46 | Re: Disabling src/test/[ssl|ldap] when not building with SSL/LDAP support |