소스 검색

Document how to write good commit messages

Based on http://gist.github.com/539516.
Tuncer Ayaz 14 년 전
부모
커밋
f76ca38e95
1개의 변경된 파일39개의 추가작업 그리고 0개의 파일을 삭제
  1. +39
    -0
      HACKING

+ 39
- 0
HACKING 파일 보기

@ -9,3 +9,42 @@ you to save this as part of custom-set-variables:
You can also tell Emacs to ignore file variables:
(setq enable-local-variables nil
enable-local-eval nil)
Writing Commit Messages
=======================
One line summary (< 50 characters)
Longer description (wrap at 72 characters)
Summary
-------
* Less than 50 characters
* What was changed
* Imperative present tense (fix, add, change)
Fix bug 42
Add 'foobar' command
Change default timeout to 42
* No period
Description
-----------
* Wrap at 72 characters
* Why, explain intention and implementation approach
* Present tense
Atomicity
---------
* Break up logical changes
* Make whitespace changes separately

불러오는 중...
취소
저장