3 ms·
It is part of the git best practices: http://git.kernel.org/?p=git/git.git;a=blob;f=Documentation/SubmittingPatches;h=ece3c77482b3ff006b973f1ed90b708e26556862;
by purephase 14y ago
It is part of the git best practices:
http://git.kernel.org/?p=git/git.git;a=blob;f=Documentation/SubmittingPatches;h=ece3c77482b3ff006b973f1ed90b708e26556862;hb=HEAD http://git.kernel.org/?p=git/git.git;a=blob;f=Documentation/...
- deleted 14y ago[deleted]
- mjs 14y agoThe HEAD version is a bit different (less clear?), although the intent is more or less the same: "describe 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." http://git.kernel.org/?p=git/git.git;a=blob;f=Documentation/SubmittingPatches;hb=HEAD http://git.kernel.org/?p=git/git.git;a=blob;f=Documentation/...
- why-el 14y agoExactly, same as when you are cherry-picking.