gtk-devel-list-request@gnome.org.) This is a good place to ask
about intended changes.
- #gimp on byxnet (irc.gimp.org, irc2.gimp.org, irc3.gimp.org,
- irc.germany.gimp.org...)s also a good place to find GTK+ developers to
- discuss changes with, however, email to gtk-devel-list is the most
- certain and preferred method.
+ #gtk+ on GIMPNet (irc.gimp.org, irc.us.gimp.org, irc.eu.gimp.org, ...)
+ is also a good place to find GTK+ developers to discuss changes with,
+ however, email to gtk-devel-list is the most certain and preferred
+ method.
1) Ask _first_.
2) There must be a ChangeLog for every commit. (If you discover that
you only committed half the files you meant to and need to fix that
up, or something, you don't need a new ChangeLog entry. But in general,
- ChangeLog entries are mandatory.) Changes with out ChangeLog entries
+ ChangeLog entries are mandatory.) Changes without ChangeLog entries
will be reverted.
3) There _must_ be a ChangeLog for every commit.
* If you are going to be changing many files in an experimental fashion,
it probably is a good idea to create a separate branch for your changes.
-* The ChangeLog entries should preferrably match in date format
+* The ChangeLog entries should preferably match in date format
with the existing entries. You can set how emacs does this
by using customize mode: