Subject: Re: small wscons.conf enhancement
To: None <email@example.com>
From: YAMAMOTO Takashi <firstname.lastname@example.org>
Date: 12/13/2005 10:32:30
> >> It's generally a good thing to include documentation when sending patches
> >> for review/comments. Or how do you plan to get docs reviewed?
> > what's wrong with reviewing/fixing documentations in cvs?
> 1) It is as hard as reviewing/fixing source in cvs.
i don't think so.
once the source change itself is reviewed,
documentation change should just reflect it.
there are no API/design problems.
> 2) including it in a (source) patch will give reviewers a rough idea of
> what the patch does before fiddling it out from the sources upfront.
do you have any trouble to read this simple patch?
> 3) it would reflect that documentation is of the same importance as
i tend to disagree. source code is more important, of course.