Typo on page "https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html".

Jonathan Wakely jwakely.gcc@gmail.com
Mon Mar 26 19:49:00 GMT 2018

Gerald, see below. Should https://gcc.gnu.org/about.html make it clear
that the pages under gcc.gnu.org/onlinedocs are not part of the
wwwdocs CVS repo, but come from the main source repo (currently SVN)

On 26 March 2018 at 20:47, Jonathan Wakely wrote:
> On 26 March 2018 at 19:51, Robin Kuzmin wrote:
>> Hey colleagues,
>> On the page
>>     https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html
>> I see:
>>     The can usually be fixed
>> I expected
>>     This can usually be fixed
>> or
>>     That can usually be fixed
>> I tried to create a patch in order to attach to this e-mail but on
>> these two pages
>>     https://gcc.gnu.org/about.html
>>     https://gcc.gnu.org/contribute.html
>> I failed to figure out how to create my username at gcc.gnu.org.
>> Based on the page
>>     https://gcc.gnu.org/about.html
>> I tried anonymous access in order to checkout the HTML files, I used
>> the command:
>>     cvs -d :pserver:cvs@gcc.gnu.org:/cvs/gcc checkout -P wwwdocs
>> but among the checked out files I fail to find the page of interest -
>> "Warning-Options.html" and I fail to find (the place to fix) by the
>> fragment of interest - "The can".
>> What I expect from you:
>> Option A: A fix of the typo on the HTML page.
>> Option B: Instructions/link about what cvs command to use in order to
>> checkout the HTML file of interest (or how to find it in the cvs
>> repository or how to browse the cvs repo).
> The HTML documentation is generated from the texinfo sources, see
> gcc/doc/invoke.texi in the GCC source tree.
>> Option C: Instructions/link about how to create my username at
>> gcc.gnu.org (for me to be able to create a patch and submit for
>> approval or to check in).
> You don't need an account on gcc.gnu.org to create a patch. You send
> the patch to the gcc-patches mailing list and somebody with write
> access checks it in.
>> Option D: Any combination of the options above (optionally
>> complemented by the updates to the corresponding pages such that I can
>> later do everything by myself to start contributing to gcc.gnu.org).

More information about the Gcc-help mailing list