Revert 8a72ebaeb39ec6cd0c6297776bee1c80a4c55cbb...3d171041a94430ddc6d445978294e014931a844f on CommitMessage

Ian Lance Taylor 2023-10-11 14:46:02 -07:00
parent 3d171041a9
commit da85f8ab81

@ -23,6 +23,7 @@ For the body (the rest of the description):
* the text should be wrapped to ~76 characters (to appease git viewing tools, mainly), unless you really need longer lines (e.g. for ASCII art, tables, or long links).
* the Fixes line goes after the body with a blank newline separating the two. (It is acceptable but not required to use a trailing period, such as `Fixes #12345.`).
* there is **no** Markdown in the commit message.
* we **do not** use `Signed-off-by` lines. Don't add them. Our Gerrit server & GitHub bots enforce CLA compliance instead.
* when referencing CLs, prefer saying "CL nnn" or using a go.dev/cl/nnn shortlink over a direct Gerrit URL or git hash, since that's more future-proof.
* when moving code between repos, include the CL, repository name, and git hash that it was moved from/to, so it is easier to trace history/blame.