Our web pages and related scripts are available via our CVS repository. You can also browse them online.
Assuming you have both CVS and SSH installed, you can check out the web pages as follows:
ssh.cvs -q -d :ext:username@gcc.gnu.org:/cvs/gcc checkout
-P wwwdocs where username is your user name at gcc.gnu.orgFor anonymous access, use
-d :pserver:cvs@gcc.gnu.org:/cvs/gcc instead.
Patches should be marked with the tag [wwwdocs] in the subject line.
When you check in changes to our web pages, they will automatically be checked out into the web server's data area.
The following is meant to provide a very quick overview of how to check in a change. We recommend you list files explicitly to avoid accidental checkins and prefer that each checkin be of a complete, single logical change.
cvs
update" before attempting a checkin; this will save you a little
time if someone else has modified that file since the last time you
synced your sources. It will also identify any files in your local
tree that you have modified.cvs diff" after applying a patch to a
local tree. Review the output to make sure that only the changes you
wanted to check in will be checked in.cvs commit" to check in the patch. You can enter
the log message via the "-m" argument to commit, or wait for
the editor window to appear.The setup of the machine running the gcc.gnu.org site is also
available, through
cvsweb and anonymous read-only CVS. Use the same procedure
as above, but use
:pserver:anoncvs@gcc.gnu.org:/cvs/sourceware for the
repository and infra for the module.
Copyright (C) Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
These pages are maintained by the GCC team. Last modified 2011-04-25.