[gtksourceview] Hacking file: move some links at the end of relevant sections
- From: Sébastien Wilmet <swilmet src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gtksourceview] Hacking file: move some links at the end of relevant sections
- Date: Sun, 17 Sep 2017 13:02:54 +0000 (UTC)
commit 4077c221f92fcdfec22f48793a2392463e41da4d
Author: Sébastien Wilmet <swilmet gnome org>
Date: Sun Sep 17 15:01:34 2017 +0200
Hacking file: move some links at the end of relevant sections
HACKING | 16 ++++++++++------
1 files changed, 10 insertions(+), 6 deletions(-)
---
diff --git a/HACKING b/HACKING
index d92dc9f..acf5605 100644
--- a/HACKING
+++ b/HACKING
@@ -55,6 +55,11 @@ conventions, but for new code it is better to follow them, for consistency.
- As a general rule of thumb, follow the same coding style as the surrounding
code.
+See also:
+https://developer.gnome.org/programming-guidelines/stable/
+https://wiki.gnome.org/Projects/GTK%2B/BestPractices
+https://wiki.gnome.org/Projects/GLib/CompilerRequirements
+
Programming best-practices
--------------------------
@@ -122,14 +127,13 @@ Here are some general advices:
writing hacks or heuristics to work around a bug or a lack of feature in an
underlying library.
-See also
---------
+See also:
+https://blogs.gnome.org/swilmet/2012/08/01/about-code-quality-and-maintainability/
+
+Other links
+-----------
-https://developer.gnome.org/programming-guidelines/stable/
-https://wiki.gnome.org/Projects/GTK%2B/BestPractices
-https://wiki.gnome.org/Projects/GLib/CompilerRequirements
http://ometer.com/hacking.html
-https://blogs.gnome.org/swilmet/2012/08/01/about-code-quality-and-maintainability/
For a shared library:
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]