D22973: docs: introduce commit message guideline
Yuri Chornoivan
noreply at phabricator.kde.org
Thu Aug 8 18:55:13 BST 2019
yurchor added a comment.
Thanks in advance for fixing these minor typos.
INLINE COMMENTS
> HACKING.md:154
> +### Footer
> +As first part of the footer additional information should be added according to the KDE Commit Policy on [special keywords](https://community.kde.org/Policies/Commit_Policy#Special_keywords_in_GIT_and_SVN_log_messages).
> +
Typo: As first part -> As the first part
> HACKING.md:156
> +
> +The rest of the footer currently must be in the format as generated by Phabricator's `ark` tool. In the future after KWin has been transitioned to KDE's GitLab instance the following holds instead:
> +
Typo: ark -> arc
> HACKING.md:161
> +
> +**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
Typo: with a space -> with space
REPOSITORY
R108 KWin
REVISION DETAIL
https://phabricator.kde.org/D22973
To: romangg, #kwin
Cc: yurchor, anthonyfieroni, zzag, ngraham, kwin, LeGast00n, sbergeron, jraleigh, fbampaloukas, GB_2, mkulinski, ragreen, jackyalcine, Pitel, iodelay, crozbo, bwowk, ZrenBot, alexeymin, himcesjf, lesliezhai, ali-mohamed, hardening, romangg, jensreuterberg, abetts, sebas, apol, mart
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kwin/attachments/20190808/7e7bcc18/attachment-0001.html>
More information about the kwin
mailing list