Tue Jan 9 08:58:06 PST 2007
- Previous message: [Slony1-general] altperl, slon_tool.conf-sample
- Next message: [Slony1-general] 1.2.6 build failure on debian etch
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mark Stosberg wrote: > Bernd Helmle wrote: > >> On Mon, 11 Dec 2006 11:47:04 -0500, Andrew Sullivan <ajs at crankycanuck.ca> wrote: >> >>> On Mon, Dec 11, 2006 at 03:05:00PM +0100, Stefan Kaltenbrunner wrote: >>> >>>> well after the latest fixes in CVS they actually work(at least i use >>>> them regulary) - and I think it is Bernds intention to take over >>>> maintainance and actively fix them ... >>>> >> Thats exactly my intention. I'm currently about to clean up the code and >> to make them to use at least strict/warning. What we need for this kind >> of tools is a reliable framework and regression tests, so that broken >> functionality could be detected. I have some ideas already... >> > > I'm also interested to help improve these tools, and expect to have some > for it as well. I agree with the approach of getting "use > strict/warnings" to work, as well as have some automated tests for the > tools. > > Should I just keep sending patches to this list for nwo, or would direct > access to an SCM system be preferable? > > If we weren't about to be migrating CVS to a new place, I'd be inclined to add you to the committers list; you've had enough good changes to warrant that, in my view. (We'd have to have some discussion amongst existing committers, but I don't imagine it would stir much controversy.) For now, by all means, patch to the list; in a couple weeks, once the world has changed, pester and we can look into direct access...
- Previous message: [Slony1-general] altperl, slon_tool.conf-sample
- Next message: [Slony1-general] 1.2.6 build failure on debian etch
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list