[GitHub] [incubator-tvm] mbaret commented on pull request #6882: [AutoScheduler] Tutorial on auto-scheduling a network for GPU

[GitBox <gi...@apache.org>]

mbaret commented on pull request #6882:
URL: https://github.com/apache/incubator-tvm/pull/6882#issuecomment-723684793


   > 
   > 
   > @mbaret you actually need everything in this PR to make the tutorial work as it describes. Since auto_scheduler is still an experimental feature in upstream and we don't need to backport other changes to v0.7.1, I think it's fine to keep as it is.
   
   Personally, the issue I find is that when commits don't describe the changes they make, it can be hard to determine what patch in history led to a certain change in behaviour (I've been burnt by this a few times now). Generally, I assume 'add tutorial' type commits won't change behaviour unless it's explicitly flagged. If all these changes are required, perhaps a middle-ground would be to flag them explicitly in the commit message?
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org