This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[libstdc++,doc] How to actually do this?
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: libstdc++ at gcc dot gnu dot org
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Sat, 12 Sep 2009 18:49:20 +0200 (CEST)
- Subject: [libstdc++,doc] How to actually do this?
I realized that since libstdc++ doesn't actually use standard GNU
documentation practices I don't actually know how to properly do
a documentation patch.
Here is one patch that I have created, and now I wonder whether
that's all I can just commit this or, if not, what further steps
I need to take.
Is there any documentation on how to change libstdc++ documentation?
Gerald
2009-09-12 Gerald Pfeifer <gerald@pfeifer.com>
* doc/xml/manual/appendix_contributing.xml: Adjust link to
coreutils.
Index: doc/xml/manual/appendix_contributing.xml
===================================================================
--- doc/xml/manual/appendix_contributing.xml (revision 151644)
+++ doc/xml/manual/appendix_contributing.xml (working copy)
@@ -922,7 +922,7 @@
<para>
Prerequisite tools are Bash 2.x,
<ulink url="http://www.doxygen.org/";>Doxygen</ulink>, and
- the <ulink url="http://www.gnu.org/software/coreutils";>GNU
+ the <ulink url="http://www.gnu.org/software/coreutils/";>GNU
coreutils</ulink>. (GNU versions of find, xargs, and possibly
sed and grep are used, just because the GNU versions make
things very easy.)