From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | YAMAMOTO Takashi <yamt(at)mwd(dot)biglobe(dot)ne(dot)jp> |
Cc: | peter_e(at)gmx(dot)net, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: tab stop in README |
Date: | 2011-08-30 02:27:13 |
Message-ID: | CA+Tgmobk41HbkbQx62bm9c8nmjWVCHCJ6HuxG=uu6Cj82iO1FA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 29, 2011 at 8:44 PM, YAMAMOTO Takashi
<yamt(at)mwd(dot)biglobe(dot)ne(dot)jp> wrote:
>> On Sun, Aug 28, 2011 at 8:28 PM, YAMAMOTO Takashi
>> <yamt(at)mwd(dot)biglobe(dot)ne(dot)jp> wrote:
>>>> On men, 2011-08-22 at 04:09 +0000, YAMAMOTO Takashi wrote:
>>>>> i know that postgresql uses ts=4 for C source code.
>>>>> but how about documatation?
>>>>
>>>> I'd say ideally don't use any tabs at all.
>>>
>>> i agree.
>>>
>>>> It appears to be geared for ts=4. Could you send a patch or other
>>>> indication for what you think needs changing?
>>>
>>> attached.
>>
>> I'm confused by this patch, because it doesn't seem to get rid of all
>> the tabs in the file. Nor does it seem to replace tabs with spaces.
>> It looks like it's just randomly removing and adding tabs in various
>> places.
>
> the patch just fixes indent for ts=4, keep using tabs.
I've applied what I believe to be an appropriate fix. I expanded the
tabs in the ASCII art but left the code examples alone.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-08-30 04:59:01 | Re: spinlocks on HP-UX |
Previous Message | YAMAMOTO Takashi | 2011-08-30 00:44:02 | Re: tab stop in README |