Mention that the mailing list is a good place to discuss patches (if they

2006-08-07  Raphael Quinet  <raphael@gimp.org>

	* HACKING: Mention that the mailing list is a good place to
	discuss patches (if they need to be discussed).
This commit is contained in:
Raphael Quinet 2006-08-07 15:15:27 +00:00 committed by Raphaël Quinet
parent 442c66484f
commit c1530eb134
2 changed files with 15 additions and 7 deletions

View File

@ -1,3 +1,8 @@
2006-08-07 Raphaël Quinet <raphael@gimp.org>
* HACKING: Mention that the mailing list is a good place to
discuss patches (if they need to be discussed).
2006-08-07 Sven Neumann <sven@gimp.org>
* plug-ins/script-fu/script-fu-interface.c (script_fu_interface):

17
HACKING
View File

@ -96,14 +96,17 @@ The interesting modules and the suggested stable branches to use are:
Patches
-------
The best way to submit patches is to 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. For the code, please try to follow the guidelines given in
Hackordnung, below. You can create the patch file with "cvs diff",
preferably with a ~/.cvsrc containing "diff -up". All kinds of
contributions are appreciated.
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. 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
to read if they contain too many comments. For the code, please try to
follow the guidelines given in Hackordnung, below. You can create the
patch file with "cvs diff", preferably with a ~/.cvsrc containing
"diff -up". All kinds of contributions are appreciated.
Autogenerated Files