Re: My plans for mod_python changes (260206).

2006-03-04 Thread Justin Erenkrantz
On 3/4/06, Graham Dumpleton [EMAIL PROTECTED] wrote: Actually, if want to get that pedantic and formalised, it does look like one can select an alternate workflow. The level of administration access we have probably does not allow us to change it, let alone see what options exist. Come up

Re: My plans for mod_python changes (260206).

2006-03-03 Thread Graham Dumpleton
On 04/03/2006, at 4:59 AM, Jim Gallacher wrote: More in the way of a general observation rather than on these specific issues, but I wouldn't necessarily mark things as resolved just on the basis of the fix being committed. For the big changes at least, I think we should see some

Re: My plans for mod_python changes (260206).

2006-03-03 Thread Jim Gallacher
Graham Dumpleton wrote: On 04/03/2006, at 4:59 AM, Jim Gallacher wrote: More in the way of a general observation rather than on these specific issues, but I wouldn't necessarily mark things as resolved just on the basis of the fix being committed. For the big changes at least, I think

Re: My plans for mod_python changes (260206).

2006-03-02 Thread Jim Gallacher
Graham Dumpleton wrote: One of the problems when I am looking at making changes to mod_python is knowing that there is some consensus that changes are a good thing, or at least that there is no objection. I feel the same way. Let's establish some policy. I'll start a separate thread for that

My plans for mod_python changes (260206).

2006-02-25 Thread Graham Dumpleton
One of the problems when I am looking at making changes to mod_python is knowing that there is some consensus that changes are a good thing, or at least that there is no objection. So far if a change was trivial, I would commit it without consultation. I have also committed some changes