summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING10
1 files changed, 9 insertions, 1 deletions
diff --git a/HACKING b/HACKING
index b35fa386..f3a901f1 100644
--- a/HACKING
+++ b/HACKING
@@ -123,16 +123,24 @@ 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.
+ - [atom] — for the Atom-namespaced code in the gdata/atom directory.
+
+ - [gd] — for the GData-namespaced code in the gdata/gd directory.
+
+ - [media] — for the Media RSS-namespaced code in the gdata/media directory.
+
- [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.
+ - [tests] — for changes to the test code in gdata/tests which are not specific to a service or namespace.
- [calendar] — for the Google Calendar code in gdata/services/calendar.
- [contacts] — for the Google Contacts code in gdata/services/contacts.
+ - [picasaweb] — for the PicasaWeb code in gdata/services/picasaweb.
+
- [youtube] — for the YouTube code in gdata/services/youtube.
The only commits which should not have a tag are translation commits, touching only the po directory.