Commit Message Format

This page is not authoritative. It is rather a collection of reasonable suggestions. Feel free to contribute to this page.

There's little technical merit to a standardized commit log format, except for much easier grepping. What we should value here is tradition.


Summary, ~50 characters, no trailing punctuation

This, that. A blank line between the summary line, and this first 
piece of free-form text. Hard wrap at 72 characters.

The other. Again, 72 characters. A blank line between this final 
piece of free-form text, and the colon-separated fields. 

First field:  value
Second field: value

General points


PR:           12345
Approved by:  John Doe <> (maintainer)
Approved by:  phk (maintainer, implicit)
Approved by:  portmgr (erwin)
Approved by:  Dow Jones (maintainer timeout, 25 days)
Submitted by: Jane Doe <>


Approved by:  maintainer
Approved by:  maintainer timeout
Approved by:  erwin (portmgr)


Reported by:  pointyhat via kris
Reported by:  pointyhat logs
Reported by:  portsmon
Submitted by: Ports Fury

Case studies

jack wrote

commit log

Maybe we should tweak abc

Suggested by: jack

Please tweak abc

Requested by: jack

Abc doesn't work, fix it!

Reported by: jack

Here's a patch

Submitted by: jack

Standard text excerpts

- Update to 1.2.3
- Take maintainership
- Pass maintainership to submitter
- Drop maintainership
Add port foo/bar: <pkg-descr follows>
- Connect foo/bar to the build
- Bump portrevision
- Fix plist
- Add rc script

CategoryHowTo CategoryStale

CommitMessageFormat (last edited 2022-11-27T23:09:32+0000 by GrahamPerrin)