This is something I've had on my disk for a few months; committed and
also activated on gcc.gnu.org.
In case anyone wonders, the reason why some snapshot was created earlier
during the day was due to me debugging something at one point. :-)
Gerald
2007-01-05 Gerald Pfeifer <[EMAIL PROTECTED]>
* crontab: Spread snapshots more evenly throughout the week, and
in "ascending" order. Build all at the same time of the day.
Index: crontab
===================================================================
--- crontab (revision 120450)
+++ crontab (working copy)
@@ -1,7 +1,7 @@
16 0 * * * sh /home/gccadmin/scripts/update_version_svn
50 0 * * * sh /home/gccadmin/scripts/update_web_docs_svn
55 0 * * * sh /home/gccadmin/scripts/update_web_docs_libstdcxx_svn
-32 22 * * 4 sh /home/gccadmin/scripts/gcc_release -s
4.0:branches/gcc-4_0-branch -l -d /sourceware/snapshot-tmp/gcc all
-32 22 * * 5 sh /home/gccadmin/scripts/gcc_release -s
4.1:branches/gcc-4_1-branch -l -d /sourceware/snapshot-tmp/gcc all
-43 17 * * 2 sh /home/gccadmin/scripts/gcc_release -s
4.2:branches/gcc-4_2-branch -l -d /sourceware/snapshot-tmp/gcc all
-43 17 * * 6 sh /home/gccadmin/scripts/gcc_release -s 4.3:trunk -l -d
/sourceware/snapshot-tmp/gcc all
+32 22 * * 0 sh /home/gccadmin/scripts/gcc_release -s
4.0:branches/gcc-4_0-branch -l -d /sourceware/snapshot-tmp/gcc all
+32 22 * * 1 sh /home/gccadmin/scripts/gcc_release -s
4.1:branches/gcc-4_1-branch -l -d /sourceware/snapshot-tmp/gcc all
+32 22 * * 3 sh /home/gccadmin/scripts/gcc_release -s
4.2:branches/gcc-4_2-branch -l -d /sourceware/snapshot-tmp/gcc all
+32 22 * * 5 sh /home/gccadmin/scripts/gcc_release -s 4.3:trunk -l -d
/sourceware/snapshot-tmp/gcc all
