From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Remove useless whitespace at end of lines |
Date: | 2010-11-24 22:54:31 |
Message-ID: | 23996.1290639271@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Wed, Nov 24, 2010 at 23:45, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>>> This was stuck in the moderation queue because of message size limit (30
>>> kB). Is it worth increasing that value?
>>
>> Evidently we should. pgindent and copyright-update commits are likely
>> to be at least this long.
> That's twice a year only - I don't see a big problem moderating those
> when it happens...
Its not so much the moderation load, as I don't like being blindsided by
commits that touch everything in sight. Finding out only when you try
to do git push (as indeed happened to me just this afternoon because of
this patch) is annoying.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-11-24 23:42:00 | pgsql: Document that a CHECKPOINT before taking a file system snapshot |
Previous Message | Bruce Momjian | 2010-11-24 22:48:40 | Re: [HACKERS] pgsql: Remove useless whitespace at end of lines |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2010-11-24 23:14:10 | Re: profiling pgbench |
Previous Message | Александър Шопов | 2010-11-24 22:53:31 | Re: Workarounds for getBinaryStream returning ByteArrayInputStream on bytea |