Steven Bosscher <[EMAIL PROTECTED]> writes: | On Monday 11 July 2005 23:34, Gerald Pfeifer wrote: | > On Mon, 11 Jul 2005, Giovanni Bajo wrote: | > >> Perhaps the wiki could automatically send all changes to gcc-patches to | > >> assist in review? | > > | > > I strongly support this (and was going to suggest this myself). I'd | > > rather it be another list though, say wiki-patches or doc-patches, | > > because of the amount of traffic that is going to be generated (think of | > > all those small typo fixes, or spam reverts). | > | > Sounds like an interesting idea! | > | > (For example, it might help those volunteering to integrate stuff from | > Wiki to the gcc/doc or wwwdocs documentation, modulo the open copyright | > assignment question.) | | Another idea that was coined on IRC is to have reviewing and commit | after approval rules for the user manual, but to allow patches to the | internals manual in without review. Is that something people are | willing to consider and discuss?
the idea that we don't review internal manual is worrysome. Some years ago, I based a work on doc/c-tree.texi (thanks Mark!). But the fact that it escaped continual revision as code gets added or improved made it a dangerous documentation, because it led to writing codes based on semantics that was no longer true. Got bugs, but don't know which side is not working prorperly. Similarly, we don't really want to let doc patches in without double-check. -- Gaby
