[gedit] hacking: ref to new file docs/gedit-development-getting-started.md
- From: Sébastien Wilmet <swilmet src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gedit] hacking: ref to new file docs/gedit-development-getting-started.md
- Date: Sun, 25 Aug 2019 16:59:18 +0000 (UTC)
commit 77cc680a0a10cbd89c010697787fcbb559ecb129
Author: Sébastien Wilmet <swilmet gnome org>
Date: Sun Aug 25 18:53:56 2019 +0200
hacking: ref to new file docs/gedit-development-getting-started.md
The idea is that more experienced developers can skip
docs/gedit-development-getting-started.md and just read the HACKING file
to know how to contribute (for the code conventions etc).
HACKING | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
---
diff --git a/HACKING b/HACKING
index 205842137..14bb673eb 100644
--- a/HACKING
+++ b/HACKING
@@ -1,3 +1,9 @@
+How to contribute to gedit
+==========================
+
+See the file `docs/gedit-development-getting-started.md` and the rest of this
+file.
+
Source code repository
======================
@@ -182,7 +188,6 @@ Here are some general advices.
See also
========
-https://wiki.gnome.org/Apps/Gedit/DevGettingStarted
https://developer.gnome.org/programming-guidelines/stable/
https://wiki.gnome.org/Projects/GTK%2B/BestPractices
http://ometer.com/hacking.html
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]