On Feb 27, 2005, at 6:17 PM, Daniel Jacobowitz wrote:
I think that you need to be a little more specific when asking a maintainer to hold off on committing a patch that he has authority to commit, desire to commit, and has been maintaining separately - out of deference to the 4.0 schedule - for many months. He would have been well within his rights to not submit a project proposal at all, and just check it in. I'm sure many larger patches will go in during Stage 1 without any coordination.
Could you explain what benefits from waiting? None of the other large, scheduled changes from 4.1 benefit from pushing this back. The only thing that it saves is one possible cause of broken bootstraps; you may as well ask no one to check in large patches, then. I'm sure plenty of people less careful than Nathanael will break bootstrap in the next few months.
And if I remember reading the difference right now, it will only break Ada bootstrap so it is not even worse off than say me applying a patch in code which is not used by default and I make a typo which causes a bootstrap failure.
-- Pinski
