Unnamed repository; edit this file 'description' to name the repository.

git clone git://
commit 4e94d1db727b6dfc2aaff23b94cc83c380ea14ec
parent 0566bbf7c7f2898fcd1d6156b27733cd48aa0449
Author: Bjørn Erik Pedersen <>
Date:   Tue,  7 Jun 2022 17:22:17 +0200

Diffstat: | 6------
1 file changed, 0 insertions(+), 6 deletions(-)
diff --git a/ b/
@@ -99,12 +99,6 @@ Most title/subjects should have a lower-cased prefix with a colon and one whites
 Also, if your commit references one or more GitHub issues, always end your commit message body with *See #1234* or *Fixes #1234*.
 Replace *1234* with the GitHub issue ID. The last example will close the issue when the commit is merged into *master*.
-Sometimes it makes sense to prefix the commit message with the package name (or docs folder) all lowercased ending with a colon.
-That is fine, but the rest of the rules above apply.
-So it is "tpl: Add emojify template func", not "tpl: add emojify template func.", and "docs: Document emoji", not "doc: document emoji."
-Please use a short and descriptive branch name, e.g. **NOT** "patch-1". It's very common but creates a naming conflict each time when a submission is pulled for a review.
 An example: