summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorPhilip Withnall <philip@tecnocode.co.uk>2009-05-07 07:37:10 +0100
committerPhilip Withnall <philip@tecnocode.co.uk>2009-05-07 07:37:10 +0100
commit2404e380873bfce8c60ee8ea43dd19f63489555b (patch)
treed125145ddcbbaac74635d39ba761f75a59d1e483 /HACKING
parent7c7edec310c636cfbe0b91ca2dc2bcc4d1ffa83c (diff)
downloadlibgdata-2404e380873bfce8c60ee8ea43dd19f63489555b.tar.gz
[docs] Updated HACKING and README
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING2
1 files changed, 2 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index 43cea4b4..b35fa386 100644
--- a/HACKING
+++ b/HACKING
@@ -123,6 +123,8 @@ The short explanation of a commit should always be prefixed by a tag to describe
- [core] — for the core code in the gdata directory, such as GDataEntry.
+ - [build] — for build changes and releases.
+
- [docs] — for documentation changes which are not specific to a service, such as updates to the docs directory, NEWS, README, this file, etc.
- [tests] — for changes to the test code in gdata/tests which are not specific to a service.