mirror of
https://github.com/subsurface/subsurface.git
synced 2024-12-01 06:30:26 +00:00
Merge git://github.com/JoachimSchipper/subsurface
* git://github.com/JoachimSchipper/subsurface: README spelling, capitalization
This commit is contained in:
commit
addfe79024
1 changed files with 3 additions and 3 deletions
6
README
6
README
|
@ -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.
|
||||
|
|
Loading…
Reference in a new issue