[Rivet] Minor problems in Rivet 1.5.0

[Frank Siegert]

Hi Andy,

On 10/05/11 14:13, Andy Buckley wrote:
> and I think we should then
> pull the singleton into the trunk, where it *will* break things.

I would prefer if this could go on a branch as long as we know that 
it'll break things (and won't be fixed within a day or so). There are 
quite a few people who are using Rivet trunk (partly because we have 
recommended this!) and might not be aware of the update freeze that they 
should adhere to. So by principle of least surprise I'd say let's leave 
trunk in a working state as far as we can.

Cheers,
Frank