Prev: pgsql: Fix a couple of oversights associated with the "physical tlist"
Next: TODO.detail removed
From: Bryce Nesbitt on 18 Apr 2008 14:46
Alvaro Herrera wrote:
>> Yes they are useful. As a new patcher, where should I look for coding
>> standards? How about a little FAQ at the
>> top of the CVS source tree?
>>
>
> The developer's FAQ is supposed to contain this kind of thing, but I
> think it's rather thin on actual details. (Some time ago it was
> proposed to create a "style guide", but people here thought it was a
> waste of time and "it will not cover what's really important", so we're
> stuck with repeating the advice over and over.)
As a new patcher I'm certain to look at the top of the CVS tree. I'm
not so certain to actually find and read a FAQ. But I've got the advice
now, so I won't make the same missteps again....

-Bryce Nesbitt

PS: less is more, keep any guide very very short....

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: pgsql: Fix a couple of oversights associated with the "physical tlist"
Next: TODO.detail removed