commit - 0662d3fab4c37977cf4e4041385367ca0cb6b4cf
commit + 61702ba622605efc0e731fd785b617714607e1ee
blob - aeeec236c1e8cacf0f4e79bacfe984922683324f
blob + 3442bd2d6e90e3dcff583321df4ea7e84fc5a0b3
--- .github/README.md
+++ .github/README.md
@@ -94,6 +94,17 @@ BRANCHES + SUBMITTING PATCHES
 Patches for portable code fixes should be based from the `linux` branch and
 sent to the mailing list for review [2] or sent to me directly (see CONTACT).
 
+Portable-specific patches should have a shortlog in the form of:
+
+```
+portable: AREA: description
+```
+
+Where `AREA` relates to the change in question (for example, `regress`,
+`libexec`, etc).  In some cases, this can be omitted if it's a generic change.
+
+This helps to delineate `-portable` changes from upstream `got`.
+
 The read-only Github repository also runs CI checks using Cirrus-CI on Linux
 and FreeBSD.
 
blob - 2dcc193feaa29ec61c388cb2aaba4b26bb478dd0
blob + 7cf7c790e8b73349d40fae822a66ceeba22f6535
--- README.portable
+++ README.portable
@@ -97,6 +97,17 @@ BRANCHES + SUBMITTING PATCHES
 Patches for portable code fixes should be based from the `linux` branch and
 sent to the mailing list for review [2] or sent to me directly (see CONTACT).
 
+Portable-specific patches should have a shortlog in the form of:
+
+```
+portable: AREA: description
+```
+
+Where `AREA` relates to the change in question (for example, `regress`,
+`libexec`, etc).  In some cases, this can be omitted if it's a generic change.
+
+This helps to delineate `-portable` changes from upstream `got`.
+
 The read-only Github repository also runs CI checks using Cirrus-CI on Linux
 and FreeBSD.