On 3/7/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
>
> We should try to keep the documentation buildable at all times so that it
> will remain visible to everyone at http://docs.python.org/dev/ .
Broken doc doesn't get pushed though. So the worst that will happen
is that the dev doc will be
[Facundo]
>> Me, for example, has an actual question to this list: "How can I know,
>> if I change something in the doc's .tex files, that I'm not broking
>> the TeX document structure?".
[MvL]
>You don't have to know. As a general contributor, just submit your
>patch, and perhaps the reviewer wil
[Scott Dial]
>While I understand that this tit-for-tat mechanism is meant to ensure
>participation, I believe in reality it doesn't, as the 400-some
>outstanding patches you referenced elswhere indicate.
. . .
>If nothing else, as an outsider there is no way to know why your patch
>gets ignored