Suggestions for improvement of the emulator

[Ivan Leo Puoti]

> This of course points to another problem with the existing system - if a patch 
> has been rejected, it should be a necessary consequence that the submitter is 
> informed with reasons - they shouldn't have to be chasing up Alexandre to 
> find out if the patch was rejected or merely missed (which happens often). 
> This is not to criticise Alexandre, but to point out that systems need to be 
> put in place to help him manage these things. Just taking patches of the 
> mailing list is not a sufficient mechanism. What is needed is a system that 
> records all patches, together with their current status (NEW, APPLIED, 
> REJECTED (with reasons), and whatever other status), informs the submitter of 
> any change, and does not allow for a patch merely to be forgotten.

I've always thought that sort of thing should be done and would be cool, maybe the guys working on 
appdb could try and come up with something?