El 19/03/13 05:15, Stan Hoeppner escribió:
On 3/18/2013 11:37 AM, Timo Sirainen wrote:
So basically you're saying that the major documentation improvement = an
index listing/describing all settings. Sure, would be useful, but I
don't see having time to write that anytime soon.
The time issue
On Tue, 19 Mar 2013 13:36:53 +0100
Joseba Torre articulated:
{snip}
Definitely, something like man 5 postconf would be really useful. I
would like to collaborate with that, but I think that my English
writing skill are not good enough.
I would be willing to assist in a project like that. If
On 19 March 2013 15:20, Jerry je...@seibercom.net wrote:
On Tue, 19 Mar 2013 13:36:53 +0100
Joseba Torre articulated:
{snip}
Definitely, something like man 5 postconf would be really useful. I
would like to collaborate with that, but I think that my English
writing skill are not good
On Mon, 2013-03-18 at 23:15 -0500, Stan Hoeppner wrote:
Do you have a way to simply dump all the current conf file parameter
names from 2.x into a single column text file?
With doveconf -d you get all the settings and also the defaults. The
docs probably should mention the defaults also.
On 3/17/2013 3:50 PM, Timo Sirainen wrote:
It's the best I can do myself. I have no idea how they could be improved in
any major way. They say that the software developer himself is the worst
possible person to write its documentation, because he can't understand what
others find
On Mon, 18 Mar 2013, Stan Hoeppner wrote:
On 3/17/2013 3:50 PM, Timo Sirainen wrote:
It's the best I can do myself. I have no idea how they could be
improved in any major way. They say that the software developer himself
is the worst possible person to write its documentation, because he
On Mon, 2013-03-18 at 10:33 -0500, Stan Hoeppner wrote:
On 3/17/2013 3:50 PM, Timo Sirainen wrote:
It's the best I can do myself. I have no idea how they could be improved in
any major way. They say that the software developer himself is the worst
possible person to write its
On Mon, Mar 18, 2013 at 11:33 AM, Stan Hoeppner s...@hardwarefreak.com
wrote:
A few things could improve the current docs in a major way.
FWIW I've found the exemplary postconf(1) almost indispensable both
for exploring the Postfix configuration and for applying impromptu
changes.
On Mon, 2013-03-18 at 18:37 +0200, Timo Sirainen wrote:
I don't know who they is. Wietse writes all the Postfix documentation
himself. It comes naturally when one performs formal software
development, not ad hoc, because documentation precedes coding. I would
assume you do ad hoc
I was going to just bite my tongue, but couldn't let this go...
On 2013-03-18 11:33 AM, Stan Hoeppner s...@hardwarefreak.com wrote:
On 3/17/2013 3:50 PM, Timo Sirainen wrote:
It's the best I can do myself. I have no idea how they could be improved in any
major way. They say that the software
On 2013-03-18 12:38 PM, Ajax aaj...@gmail.com wrote:
FWIW I've found the exemplary postconf(1) almost indispensable both
for exploring the Postfix configuration and for applying impromptu
changes.
I think most everyone would agree that postfix is in a class by itself
when it comes to code
On 18.03.2013, at 17:37, Timo Sirainen t...@iki.fi wrote:
Because it significantly increases development times, and when you're
basically doing everything yourself there's nobody else reading those
anyway.
From my point of view: do continue the very same way every since writing
your first
On 3/18/2013 11:37 AM, Timo Sirainen wrote:
So basically you're saying that the major documentation improvement = an
index listing/describing all settings. Sure, would be useful, but I
don't see having time to write that anytime soon.
The time issue is perfectly understandable Timo.
My
13 matches
Mail list logo
