RE: The 0.18.0 release and Repository Rules

> 	Its come to my attention that the repository hasn't 
> been in the best 
> of shape in the last few days. This is probably my fault :) . But 
> regardless, it seems that its about time to start putting 
> some process 
> around CVS commits. Starting now :
> 
> 	1) Send me patches / diffs of all proposed changes and get my 
> approval. There are a number of cooks in this pot right now 
> and I need 
> to make sure I know what's going in :)

Would it be possible to create a "patch" directory within the current
repository for patch files? Would make it a lot easier to submit patches
and make sure nothing gets lost or overlooked. Commit the patch up, then
message/email you that there is one pending. Then all you'd have to do
is run 'patch' against all the files and you're done.

When you know you don't need a particular patch file any more it's a
simple matter to cvs remove it.



Shay

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.445 / Virus Database: 250 - Release Date: 1/21/2003