diff options
| author | Philip Withnall <philip@tecnocode.co.uk> | 2013-11-24 18:26:28 +0000 |
|---|---|---|
| committer | Philip Withnall <philip@tecnocode.co.uk> | 2013-11-24 18:26:28 +0000 |
| commit | ac59d7a6903bf9708d41999d46a6356fb87709c2 (patch) | |
| tree | 5c06df270cf8bc0dfc4c62f9318b2a64f0880533 /HACKING | |
| parent | d663cbff8a733d0296e81dc84c3ae6a307cb9b58 (diff) | |
| download | libgdata-ac59d7a6903bf9708d41999d46a6356fb87709c2.tar.gz | |
docs: Update libgdata website
Now: https://wiki.gnome.org/Projects/libgdata
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -162,7 +162,7 @@ Commit messages =============== libgdata does not use a ChangeLog; it is auto-generated from the git log when packaging a release. Commit messages should follow the GNOME commit -message guidelines (http://live.gnome.org/Git/CommitMessages), with the exception that when a commit closes a bug, the short explanation of the commit +message guidelines (https://wiki.gnome.org/Git/CommitMessages), with the exception that when a commit closes a bug, the short explanation of the commit should simply be the bug's title, as copied from Bugzilla (e.g. "Bug 579885 – Add code examples to documentation"). The long explanation should then be used to give details of the changes. If the bug's title is not relevant, it should be changed before committing the changes. |