Paul, If it's ok, I'd prefer if you did these changes to an offline repository. I don't really know what exactly your changes would be (as tempting as they sound) and what all the implications would be, so I would prefer to review them from a separate source. Otherwise I would very much appreciate your help in getting us up to speed with the latest version of Avalon, a better structure, and otherwise improved build process as you see it. -- Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/
Paul Hammant wrote: > Danny, > >>> Nonetheless, I'd like to offer my services to bring you completely up to >>> date with released Avalon comps. >>> >> >> +1 >> > You guys need to worry about how to make me committer for this once off > duty.. Normal rules of patches before proposition have not been followed. > > I could cut the whole thin else where (without CVS directories) and let > one of you over lay it before commit. > >> My specific concern is that there seem to be a significant number of >> avalon >> issues manifesting themselves as James bugs. >> What I think James needs is a way in which we can address bugs and >> enhancements without getting too dirty in the avalon code. >> > You must realise that JAMES is our flagship dependant project... we will > always be attentive to you... > > - Paul -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
