> I think that someone, though, should be committed to fixing this pass ASAP > after it's checked in; waiting until late August to fix it seems bad. Is > there someone else who can commit to working on it as a high priority after > the main tuples checkin?
I would obviously vote in favor of removal if the pass is unmaintained, but if it is agreed that it will be maintained, I can commit to working on it as soon as we merge. If it is maintained, I would count on having the maintainers provide me some consulting help throughout the conversion :). Aldy
