> "Nathan" == Nathan Bush writes:
>>> 372 P3 webrev does not display executable bit change
Rich> It never did for Teamware, which also propagated these. This is P3
Rich> why?
[...]
Nathan> Since we will be enforcing a policy that the executable bit
Nathan> should never be set, and have oth
> "Rich" == Richard Lowe writes:
>> 264 P3 revisit nightly -O and friends for Mercurial
Rich> You were doing that, right Mike? (I know I can't)
Right. The fix is currently being tested.
>> * Old Style, Copyright, etc Issues
[...]
>> 4633617 P4 wx copyright is even slower
>> 4678979 P4 w
On Mon, Nov 05, 2007 at 10:32:35AM -0800, Mike Kupfer wrote:
> Rich mentioned that changing to 0.9.5 may cause some problems for the
> Xen folks, but I'm still a little unclear on the details. I'm hoping
There is no problem that should block stuff going back into Nevada, as we don't
(yet) us
Richard Lowe wrote:
> Mike Kupfer writes:
>> * Webrev
>>
>> These do not appear to be stoppers for SFW:
>>
>> 374 P3 setting CODEMGR_WS confuses webrev
>
> I'll look at this soon, if I really have to.
Don't worry, I'm already working on it.
>> 372 P3 webrev does not display executab
Richard Lowe writes:
>> 370# P3 RTI checks should tell me I can't connect, or otherwise f...
>
> I can't fix that either, given my prior adventures in that code have
> been so disastrous, thanks to me being able to run it. It (and the
> XML thing we'd talked about) need to be done by somebod
Mike Kupfer writes:
> I just finished going over the lists in Bugzilla (bugs.grommit.com) and
> Bugster. Stephen and a couple other senior engineers are particularly
> interested in what needs to be fixed before we can think about moving
> SFW, so my comments are biased in that direction. There
I just finished going over the lists in Bugzilla (bugs.grommit.com) and
Bugster. Stephen and a couple other senior engineers are particularly
interested in what needs to be fixed before we can think about moving
SFW, so my comments are biased in that direction. There appear to be
several clumps o
