From patchwork Sat Jan 8 16:54:50 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Gerald Pfeifer X-Patchwork-Id: 77969 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) by ozlabs.org (Postfix) with SMTP id 03296B7125 for ; Sun, 9 Jan 2011 03:55:07 +1100 (EST) Received: (qmail 4032 invoked by alias); 8 Jan 2011 16:55:04 -0000 Received: (qmail 4024 invoked by uid 22791); 8 Jan 2011 16:55:03 -0000 X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL, BAYES_05, HK_OBFDOM, RCVD_IN_DNSWL_LOW, SPF_SOFTFAIL, TW_WW X-Spam-Check-By: sourceware.org Received: from relay02.pair.com (HELO relay02.pair.com) (209.68.5.16) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Sat, 08 Jan 2011 16:54:56 +0000 Received: (qmail 48296 invoked from network); 8 Jan 2011 16:54:53 -0000 Received: from 188.118.200.192 (HELO trevally) (188.118.200.192) by relay02.pair.com with SMTP; 8 Jan 2011 16:54:53 -0000 X-pair-Authenticated: 188.118.200.192 Date: Sat, 8 Jan 2011 17:54:50 +0100 (CET) From: Gerald Pfeifer To: gcc-patches@gcc.gnu.org Subject: [wwwdocs] Further shorten cvs.html Message-ID: MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Delivered-To: mailing list gcc-patches@gcc.gnu.org This further shortens cvs.html to the point where I hope it's easier to consume for newcomers now. Thanks again to Mingjie Xing for making me focus on this. Gerald Index: cvs.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/cvs.html,v retrieving revision 1.218 diff -u -r1.218 cvs.html --- cvs.html 6 Jan 2011 11:16:43 -0000 1.218 +++ cvs.html 8 Jan 2011 16:41:10 -0000 @@ -12,36 +12,24 @@

Our web pages and related scripts are available via our CVS repository. You can also browse them -online using cvsweb.

+online.

Using the CVS repository

Assuming you have both CVS and SSH installed, you can check out the web pages as follows:

-
    +
    1. Set CVS_RSH in your environment to ssh.
      2. -
    2. Set CVSROOT in your environment to - :pserver:cvs@gcc.gnu.org:/cvs/gcc.  - Alternately add - -d :pserver:cvs@gcc.gnu.org:/cvs/gcc - immediately after cvs in the commands below.
      3. -
    3. cvs -qz9 checkout -P wwwdocs
      4. +
    4. cvs -qz -d :ext:username@gcc.gnu.org:/cvs/gcc checkout +-P wwwdocs where username is your user name at gcc.gnu.org
    -

    Patches should be marked with the tag [wwwdocs] in the subject line.

    - -
    -

    Read-write CVS access

    +

    For anonymous access, use +-d :pserver:cvs@gcc.gnu.org:/cvs/gcc instead.

    -

    Check out things by setting environment variables as above and -and issuing the command

    - -

    -cvs -z 9 -d :ext:username@gcc.gnu.org:/cvs/gcc co wwwdocs -

    +

    Patches should be marked with the tag [wwwdocs] in the subject line.

    -

    where username is your user name at gcc.gnu.org.

    Checking in a change

    @@ -49,14 +37,10 @@

    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. It is not meant to be a replacement for the CVS -manual.

    - -

    In all the commands listed below, you can give an explicit list of -filenames to the cvs command. We recommend you list files explicitly +

    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, which may affect multiple files.

    +complete, single logical change.

    1. Sync your sources with the master repository via "cvs @@ -71,8 +55,7 @@
    2. Use "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 and enter the log message in the editor -window.
      3. +the editor window to appear.
    3. Upon successfull checkin a message will be sent to the gcc-cvs-wwwdocs mailing list.