File: README.svn-commit

package info (click to toggle)
gambas3 3.1.1-2
  • links: PTS
  • area: main
  • in suites: wheezy
  • size: 44,632 kB
  • sloc: ansic: 94,949; cpp: 76,426; sh: 19,667; makefile: 1,180; cs: 342; perl: 184; xml: 34
file content (53 lines) | stat: -rw-r--r-- 1,343 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
STANDARD FORMAT FOR COMMIT MESSAGES
-----------------------------------

This message is for Laurent, Daniel, and all people that will have a write 
access to the svn repository in the future.

I want to have a standard way to write commit messages, so that ChangeLog can 
be almost automatically generated.

The format is the following:

* A ChangeLog slot, between '[' & ']'
* A ChangeLog modification: a '*', a space, the word 'BUG','NEW' or 'OPT', a 
colon, a space, and the text.

'BUG' for a fix, 'NEW' for a new feature, and 'OPT' for an optimization.

Slots are the name of the component, in uppercase if possible, or some other 
slots like [INTERPRETER], [COMPILER]...

All lines lengths must be lower or equal than 76 characters.

If a changelog modification is more than one line, you must use a two space 
indent.

Void lines are ignored.

All other lines won't go into the changelog.

For example:

--8<-----------
I did this thing, and this won't go into the changelog.

[GB.QT]
* BUG: I fixed this bug.
* NEW: I made this very long modification....
  and it takes more than one line to write it.

This won't go into the changelog too.

[GB.SDL]
* BUG: What an awful bug!

[GB.GTK]
* NEW: I finally finished the component :-)

--8<-----------

It would be cool to follow this scheme. I will start at my next commit.

-- 
Benoit.