For the future, a patch that touches different components must be split in commits per component. Right now that commit has nothing to do with kamdbctl. Overall, it is not something critical, but is good to keep the commit message coherent with what it does, because the commits history is used quite often to try to track back changes.
I am going to merge it, thanks.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.