On Wed, 2009-07-08 at 23:08 +0200, Øyvind Harboe wrote:
> On Wed, Jul 8, 2009 at 11:00 PM, Zach Welch<[email protected]> wrote:
> > I just saw you did re-post... but you only waited 4 hours.  That is not
> > enough time.  You need to wait 12-24 hours, preferably 24.
> 
> 24h it is until 0.2 is out then.

Let me try to clarify a little.  For code, 24 hours is good.  For docs,
12 hours probably is enough (particularly after a full ACK).  That is
long enough for everyone to revisit the list.  Some patch churn in the
docs does not seem as blasphemous to me as patch churn in the code, for
some reason.  Anyone care to try and explain that bit of reasoning? :)  

I suppose it may be from the fact that "clean patching" of documentation
seems difficult beyond its value; I often can't grok the patch alone, so
I have to apply it to review.   Clean patching of code is easier (when
it has a good style), and they can be easier to review without applying.
Is that rational, or rationalization? ;)

Cheers,

Zach
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to