| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: updated emacs configuration |
| Date: | 2014-01-29 05:53:02 |
| Message-ID: | 17278.1390974782@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> If this only affects a handful of places, then sure, let's go ahead
> and fix it. But if it's going to create a massive enough diff that
> we've gotta think about back-patching it, then IMHO it's totally not
> worth it.
A quick grep search says there are well over 3000 comment lines containing
'.' followed by a tab. grep isn't smart enough to tell if the tabs expand
to exactly two spaces, but I bet the vast majority do. So it might not
be quite as bad as the 8.1 wrap-margin change, but it'd be extensive.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-01-29 06:43:29 | Re: WIP patch (v2) for updatable security barrier views |
| Previous Message | Tom Lane | 2014-01-29 05:43:40 | Re: ALTER TABLE lock strength reduction patch is unsafe |