[m-dev.] cvs tags for latest stable & unstable releases

[Fergus Henderson]

Hi,

I've modified tools/test_mercury so that the nightly cron tests
now tag the files in the repository with tags like
`unstable-rotd-i686-pc-linux-libc2_0-gnu' when the bootstrap
passes and `stable-rotd-i686-pc-linux-libc2_0-gnu' when all the
tests pass.

If you're doing cvs updates, you may find that updating to
the latest stable rotd for the particular platform in question
is in general a bit more reliable than updating to the head revision.
Doing that will ensure that your local workspace is more insulated
against bugs that make it into the cvs repository.

The tags may also be helpful for finding bugs;
if the tests fail, you can to a `cvs diff -rstable-rotd-...'
to find out what has changed since they last succeeded.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>  |  of excellence is a lethal habit"
PGP: finger fjh at 128.250.37.3        |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------