Jonathan: that's right. I've chatted with Robert maybe or some other core dev and thay insist we have to create Commit object to get template message and then discard it. But this is going against qbzr/qcommit architecture. What if user changes the files selected for commit? If commit template uses list of files to commit then when user changes the list of files we need to re-build template? Very quickly things will become very complex to handle.
Jonathan: that's right. I've chatted with Robert maybe or some other core dev and thay insist we have to create Commit object to get template message and then discard it. But this is going against qbzr/qcommit architecture. What if user changes the files selected for commit? If commit template uses list of files to commit then when user changes the list of files we need to re-build template? Very quickly things will become very complex to handle.