summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPhilip Withnall <philip@tecnocode.co.uk>2015-05-03 23:48:35 +0100
committerPhilip Withnall <philip@tecnocode.co.uk>2015-05-03 23:48:35 +0100
commitf5f4d75bc63fb57bf344ff1018731e12d695772e (patch)
treedbd83507891641ff3ca4c48d3f1f4d1830208b07
parentf73d69de95bb934a34b20644de5e84854d046284 (diff)
downloadlibgdata-f5f4d75bc63fb57bf344ff1018731e12d695772e.tar.gz
docs: Remove a dead link from the HACKING file
https://bugzilla.gnome.org/show_bug.cgi?id=664353
-rw-r--r--HACKING2
1 files changed, 1 insertions, 1 deletions
diff --git a/HACKING b/HACKING
index 587b5b8e..69177c23 100644
--- a/HACKING
+++ b/HACKING
@@ -138,7 +138,7 @@ In general, use common sense. However, there are some specific cases where a sta
- For boolean setters use foo_bar_set_is_baz, rather than foo_bar_set_baz.
- In general, try to keep API named similarly to the actual GData API constructs. In certain cases, however, it might make more sense to rename pieces
- of API to be less cryptic (e.g. "timezone" instead of "ctz": http://code.google.com/apis/calendar/docs/2.0/reference.html#Parameters).
+ of API to be less cryptic (e.g. "timezone" instead of "ctz").
Deprecating public API
======================