Will apply the rule to meta schedule RFC this weekend
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/17#issuecomment-898812676
Thanks for the update. I'm glad to see that we're refining the RFC process as
it goes into production.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/17#issuecomment-895676508
cc @junrushao1994 would be great if you can send a followup PR to rename the
autoTIR RFC, and update links
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/17#issuecomment-895207508
Merged #17 into main.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/17#event-5129597476
let us wait for another two days and if there is no objection, we can merge it
in
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/17#issuecomment-893562583
Yes we can udpdate the merged RFC, the only one I am aware of is autoTIR RFC
and perhaps @junrushao1994 can chime in
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/17#issuecomment-892
I like the idea. It follows the common practice in previous communities and
simplifies the RFC process.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/17#issuecomment-892770698
Hi all,
After some discussion, we'd like to propose that RFCs are numbered
according to the GitHub PR number. This follows the idea of documenting those
RFCs which are rejected. While it adds an extra step to the initial RFC
posting, it simplifies all future references by not allocating two dif
