diff options
| author | Tomi Ollila <tomi.ollila@iki.fi> | 2013-02-12 10:46:27 +0200 |
|---|---|---|
| committer | Tomi Ollila <tomi.ollila@iki.fi> | 2013-02-12 10:46:27 +0200 |
| commit | 09362e87f771dd37a5f04854499db0158c0c823c (patch) | |
| tree | 617101c7b600f22a9fda7bbd1d1a852f2f196231 | |
| parent | 1b2ec15324d8476ea40baf8263a91695f4a45713 (diff) | |
bold `git log`...
| -rw-r--r-- | contributing.mdwn | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/contributing.mdwn b/contributing.mdwn index d7faa03..11d711b 100644 --- a/contributing.mdwn +++ b/contributing.mdwn @@ -58,7 +58,7 @@ Each commit should contain one logical change only. The code should build and the tests should pass after each commit. Changes to lib, cli, emacs, tests, man pages, or news are usually best kept separate. Also separate cleanups from functional changes. See the -Notmuch source history (`git log`) for examples. +Notmuch source history (**`git log`**) for examples. For in-depth discussion on the subject, see [Software Release Practice HOWTO](http://tldp.org/HOWTO/Software-Release-Practice-HOWTO/) by Eric S. Raymond. @@ -74,8 +74,8 @@ See also on commit guidelines, including commit messages. It is customary to prefix the subject line with "lib:", "cli:", "emacs:", -etc. depending on which part of Notmuch the commit is changing. See `git log` -for examples. +etc. depending on which part of Notmuch the commit is changing. See +**`git log`** for examples. Wrap the lines to about 72 characters. |