I think you should usually be able to reword any "self-action" commits into system action commits.
For example, you could say "Don't issue unnecessary cache directory warning".
Prefacing a commit message with add/remove/delete seems unnecessary.
For example, you could say "Don't issue unnecessary cache directory warning".
Prefacing a commit message with add/remove/delete seems unnecessary.
> you should usually be able to reword any "self-action" commits into system action commits
So your suggestion here is completely irrelevant, as "system" doesn't refactor anything.
Describe your changes in imperative mood, e.g. "make xyzzy do frotz" instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to do frotz", as if you are giving orders to the codebase to change its behaviour.
Or, if you prefer not to anthropomorphize the codebase (because it hates that), you could also think of it as instructing someone to make the change (and then supplying a patch implementing that instruction).
And a quick search through the Linux kernel git log turns up 1416 messages of the form "subsystem: Refactor ...".