This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[www] reliable method for checking out a date on a branch
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: gcc at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Mon, 23 Dec 2002 09:28:06 -0800
- Subject: [www] reliable method for checking out a date on a branch
The method for checking out a particular date on a branch described in
"How to Locate GCC Regressions" turned out to have problems sometimes.
This one works. Checked in, after validation at http://validator.w3.org.
Janis
Index: reghunt-howto.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/reghunt-howto.html,v
retrieving revision 1.2
diff -u -r1.2 reghunt-howto.html
--- reghunt-howto.html 20 Dec 2002 20:32:20 -0000 1.2
+++ reghunt-howto.html 23 Dec 2002 17:19:23 -0000
@@ -107,23 +107,21 @@
<h3>CVS branches</h3>
-<p>CVS doesn't provide a straightforward way to check out a branch for a
-particular date, but this method seems to work. To get the first date
-to test, do:</p>
+<p>To get all files for a particular date on the branch, check out the
+branchpoint and then update with all changes between the branchpoint and
+the desired date. For example,</p>
<pre>
+ BRANCH="gcc-3_2-branch"
+ DATE="2002-09-01"
rm -rf gcc
- cvs co -r <i>branch</i> gcc
- cvs up -j <i>branch</i> -j <i>branch</i>:"<i>date</i>"
+ cvs co -r ${BRANCH}point gcc
+ cvs up -d -j${BRANCH}point -j${BRANCH}:"${DATE}"
</pre>
-<p>For additional dates do the following, which works even when the next
-date is earlier than the previous date:</p>
-
-<pre>
- cvs up -j <i>branch</i>:"<i>prev_date</i>" \
- -j <i>branch</i>:"<i>next_date</i>"
-</pre>
+<p>This method works reliably when it starts with a clean checkout.
+Further updates that use the previous date and a new date sometimes run
+into problems, with a few files not being updated correctly.</p>
<h2><a name="build_gcc">Build GCC</a></h2>