From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24677 invoked by alias); 19 Jan 2020 12:49:35 -0000 Mailing-List: contact gcc-cvs-wwwdocs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-cvs-wwwdocs-owner@gcc.gnu.org Received: (qmail 24523 invoked by uid 9022); 19 Jan 2020 12:49:25 -0000 Date: Sun, 19 Jan 2020 12:49:00 -0000 Message-ID: <20200119124925.24519.qmail@sourceware.org> From: gerald@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. ddcd8e320e44dcbbe5dbd6813f48f7b6143d6572 X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: 8baef5d5cbd5717551b0897520b835f5b7054218 X-Git-Newrev: ddcd8e320e44dcbbe5dbd6813f48f7b6143d6572 X-SW-Source: 2020/txt/msg00051.txt This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via ddcd8e320e44dcbbe5dbd6813f48f7b6143d6572 (commit) from 8baef5d5cbd5717551b0897520b835f5b7054218 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit ddcd8e320e44dcbbe5dbd6813f48f7b6143d6572 Author: Gerald Pfeifer Date: Sun Jan 19 13:48:43 2020 +0100 Adjustments of "regression hunting" instructions to the post-SVN world. With Git a clone carries the whole repository, so remove instructions on obtaining a local copy of the repository and related instructions on SVN usage. On the way remove a web link for the contrib/reghunt scripts since those are in the repository anyway. diff --git a/htdocs/bugs/reghunt.html b/htdocs/bugs/reghunt.html index d9c92067..48d7d241 100644 --- a/htdocs/bugs/reghunt.html +++ b/htdocs/bugs/reghunt.html @@ -54,9 +54,8 @@ while the range is too large to investigate by hand:

The first three steps are described below. They can be automated, -as can the framework for the binary search. The directory -contrib/reghunt in the GCC repository includes +as can the framework for the binary search. The directory +contrib/reghunt in the GCC repository includes scripts to do this work.

There are several short cuts @@ -70,58 +69,13 @@ are simple to work around.

Get GCC sources

-

Get a Local Copy of the GCC repository

- -

Using rsync to get a local copy of the GCC -repository is highly recommended for regression hunts. You'll -be checking out the tree used for the regression search over and over -again and won't want to affect access times for other GCC developers -who are using the real repository, and it will also be faster for -you.

- -

The full tree takes a lot of disk space, but it's possible to -exclude directories you won't need for your hunt. If you're already -using a local SVN repository via rsync, -you can make a cut-down version of it that leaves out directories you -don't need for the regression hunt. This makes SVN operations much -quicker, making it worthwhile even if the copy is on the same system. -It's particularly useful if you'll want to copy it to a system that is -low on available disk space. The following, for example, makes a -smaller copy of the repository that can be used for finding C and C++ -compile-time problems and takes only half the disk space as the full -repository.

- -
-    cat <<EOF > rsync_exclude
-    --exclude=gcc-svn/benchmarks
-    --exclude=gcc-svn/boehm-gcc
-    --exclude=gcc-svn/old-gcc
-    --exclude=gcc-svn/wwwdocs
-    --exclude=gcc-svn/gcc/libstdc++-v3
-    --exclude=gcc-svn/gcc/gcc/ada
-    --exclude=gcc-svn/gcc/gcc/testsuite
-    EOF
-
-    tar `cat rsync_exclude` -cf - gcc-svn | gzip > gcc-svn.tar.gz
-
- -

Check Out a Working Copy

-

Check out a local working copy of -GCC from your local repository. If you are not using a local -repository, then check out a working copy using anonymous read-only SVN access. In any case, -use a new working copy that is separate from what you use for +

Check out a working copy using Git. +Use a new working copy that is separate from what you use for development or other testing, since it is easy to end up with files in strange states.

-

Information about checking out specific dates, working with branches and tags, and -inspecting the commit logs is available at the SVN Help pages in the GCC -Wiki.

-

Branch and release dates

----------------------------------------------------------------------- Summary of changes: htdocs/bugs/reghunt.html | 54 ++++-------------------------------------------- 1 file changed, 4 insertions(+), 50 deletions(-) hooks/post-receive -- gcc-wwwdocs