Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-06 Thread Chris Pickett
Gerald Pfeifer wrote: Chris, I see you have not received any response to this yet, so let me give it a try. Thanks! I unsubscribed from the list and was surprised to see this in my inbox. Please continue to CC me on replies. On Sat, 28 Oct 2006, Chris Pickett wrote: 5. Fix what I have

Clarify policy on documentation changes [wwwdocs]

2007-01-06 Thread Gerald Pfeifer
I just committed the patch below which clarifies that maintainers are allowed to make/approve changes to those parts of our documentation that are related to their area of maintainership. This is not a change in policy, just a clarification, but since there has been some uncertainty in this area

Re: Do we want non-bootstrapping "make" back?

2007-01-06 Thread Paolo Bonzini
Richard Kenner wrote: Not much. I'm convinced it would be feasible, but definitely not easy, so I wanted to see how much interest there was - seems like some, but not a lot. Would this comprise retrofitting the support into the 4.2 branch? I don't think it's needed in the 4.2 branch since you

Re: We have no active maintainer for the i386 port

2007-01-06 Thread Kaveh R. GHAZI
On Sat, 6 Jan 2007, Steven Bosscher wrote: > Hi, > > We currently do not have an active maintainer for the i386 port. The > only listed maintainer for the port is rth, and he hasn't been around > to approve patches in a while. This situation is a bit strange for > a port that IMHO is one of the

Re: We have no active maintainer for the i386 port

2007-01-06 Thread H. J. Lu
On Sat, Jan 06, 2007 at 04:42:27PM +0100, Steven Bosscher wrote: > Hi, > > We currently do not have an active maintainer for the i386 port. The > only listed maintainer for the port is rth, and he hasn't been around > to approve patches in a while. This situation is a bit strange for > a port t

We have no active maintainer for the i386 port

2007-01-06 Thread Steven Bosscher
Hi, We currently do not have an active maintainer for the i386 port. The only listed maintainer for the port is rth, and he hasn't been around to approve patches in a while. This situation is a bit strange for a port that IMHO is one of the most important ports GCC has... In the mean time, pat