HACKING: patches: recommend git-format-patch, not a repo to fetch from
Also update the developer mailing list address.
(cherry picked from commit d3506a13fc
)
This commit is contained in:
9
HACKING
9
HACKING
@ -88,14 +88,13 @@ part of recent Linux distribution releases.
|
|||||||
Patches
|
Patches
|
||||||
-------
|
-------
|
||||||
|
|
||||||
The best way to submit patches is to publish your git repository and
|
The best way to submit patches is to provide files created with
|
||||||
ask developers to git-fetch from you.
|
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
|
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
|
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
|
it to the gimp-developer-list@gnome.org mailing list.
|
||||||
create the patch file with git-format-patch
|
|
||||||
|
|
||||||
If the patch needs to be discussed, you should also consider using the
|
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
|
mailing list instead of Bugzilla because bug reports tend to be hard
|
||||||
|
Reference in New Issue
Block a user