diff options
author | Joachim Schipper <joachim@joachimschipper.nl> | 2011-11-27 17:53:14 +0100 |
---|---|---|
committer | Joachim Schipper <joachim@joachimschipper.nl> | 2011-11-27 18:42:00 +0100 |
commit | aeb367e0a7bbcb280fef33083ae599602ed91951 (patch) | |
tree | f4bb41d12b1fd2acfafcb231f74681f4deeb7bd0 /README | |
parent | 19356de24620c75c26152c5f19947c8a1e5215cb (diff) | |
download | subsurface-aeb367e0a7bbcb280fef33083ae599602ed91951.tar.gz |
README spelling, capitalization
Spelling: paragrahps -> paragraphs.
Update the README's example commit message to start with a capital
letter. Capitalize "Java".
Signed-off-by: Joachim Schipper <joachim@joachimschipper.nl>
Diffstat (limited to 'README')
-rw-r--r-- | README | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -1,6 +1,6 @@ Half-arsed divelog software in C. -I'm tired of java programs that don't work etc. +I'm tired of Java programs that don't work etc. License: GPLv2 @@ -161,13 +161,13 @@ See: http://gerrit.googlecode.com/svn/documentation/2.0/user-signedoffby.html Also, please write good git commit messages. A good commit message looks like this: - header line: explaining the commit in one line + Header line: explaining the commit in one line Body of commit message is a few lines of text, explaining things in more detail, possibly giving some background about the issue being fixed, etc etc. - The body of the commit message can be several paragrahps, and + The body of the commit message can be several paragraphs, and please do proper word-wrap and keep columns shorter than about 74 characters or so. That way "git log" will show things nicely even when it's indented. |