[gimp/gimp-2-8] HACKING: patches: recommend git-format-patch, not a repo to fetch from
- From: Michael Natterer <mitch src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gimp/gimp-2-8] HACKING: patches: recommend git-format-patch, not a repo to fetch from
- Date: Sun, 7 Oct 2012 13:21:24 +0000 (UTC)
commit ec9ed96fd7ed83a2fc792e5a92e913acb74a6240
Author: Michael Natterer <mitch gimp org>
Date: Sun Oct 7 15:18:14 2012 +0200
HACKING: patches: recommend git-format-patch, not a repo to fetch from
Also update the developer mailing list address.
(cherry picked from commit d3506a13fc3dce0ace269ba8637ea8914597381b)
HACKING | 9 ++++-----
1 files changed, 4 insertions(+), 5 deletions(-)
---
diff --git a/HACKING b/HACKING
index ea49310..39e0929 100644
--- a/HACKING
+++ b/HACKING
@@ -88,14 +88,13 @@ part of recent Linux distribution releases.
Patches
-------
-The best way to submit patches is to publish your git repository and
-ask developers to git-fetch from you.
+The best way to submit patches is to provide files created with
+git-format-patch.
-For bug fixes where the patch is small you can file a bug report at
+It is recommended that you file a bug report at
http://bugzilla.gnome.org/ and attach your patch to it as a plain text
file, not compressed. If your patch is reasonably small you can submit
-it to the gimp-developer lists xcf berkeley edu mailing list. You can
-create the patch file with git-format-patch
+it to the gimp-developer-list gnome org mailing list.
If the patch needs to be discussed, you should also consider using the
mailing list instead of Bugzilla because bug reports tend to be hard
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]