hogepodge commented on pull request #2:
URL: https://github.com/apache/tvm-rfcs/pull/2#issuecomment-829380288
Doesn't look like there's much conversation around this. I'm ready to move
forward on it when you think it's appropriate.
https://discuss.tvm.apache.org/t/rfc-preparing-to-la
hogepodge commented on pull request #2:
URL: https://github.com/apache/tvm-rfcs/pull/2#issuecomment-826137128
Ok, that clears things up for me. Thanks. @tqchen I've updated the PR to
move more of the mechanics of handling the RFC into the tracking issue, and
deleted the requirements for mo
hogepodge commented on pull request #2:
URL: https://github.com/apache/tvm-rfcs/pull/2#issuecomment-826137128
Ok, that clears things up for me. Thanks. @tqchen I've updated the PR to
move more of the mechanics of handling the RFC into the tracking issue, and
deleted the requirements for mo
hogepodge commented on pull request #2:
URL: https://github.com/apache/tvm-rfcs/pull/2#issuecomment-825909082
@tqchen @jroesch I updated the process to more closely match the Rust
process. A few comments on it:
* I still kept it more lightweight than the Rust process. As a smaller
c
hogepodge commented on pull request #2:
URL: https://github.com/apache/tvm-rfcs/pull/2#issuecomment-823499136
@areusch @tqchen @jroesch ready for final review
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL ab
