diff options
author | Stefano Karapetsas <[email protected]> | 2012-10-27 16:44:58 +0200 |
---|---|---|
committer | Stefano Karapetsas <[email protected]> | 2012-10-27 16:44:58 +0200 |
commit | 2ebc394a1ae159238254696fe0cb487528ee239b (patch) | |
tree | fe1b282e1e44fa8b9a50be29bfe8affc86110866 | |
parent | ae46e7dc17aa620b25cae52a8c576022ecc1c66b (diff) | |
download | mate-control-center-2ebc394a1ae159238254696fe0cb487528ee239b.tar.bz2 mate-control-center-2ebc394a1ae159238254696fe0cb487528ee239b.tar.xz |
update README
-rw-r--r-- | README | 18 |
1 files changed, 7 insertions, 11 deletions
@@ -12,13 +12,13 @@ See the file 'INSTALL' How to report bugs - -Bugs should be reported to the MATE bug tracking system under the product -control-center. It is available at http://bugzilla.gnome.org. +Bugs should be reported to the MATE bug tracking system under github: + https://github.com/mate-desktop/mate-control-center/issues In the report please include the following information - Operating system and version - For Linux, version of the C library + For Linux, version of the C and glib libraries How to reproduce the bug if possible If the bug was a crash, include the exact text that was printed out A stacktrace where possible [see below] @@ -43,11 +43,7 @@ Once you have the backtrace, copy and paste this either into the Patches - -Patches should be submitted to bugzilla.gnome.org or emailed to the [email protected] list. If using bugzilla, attach -the patch to a new bug report [or preferably, check to see if there is -already a bug report that corresponds to your patch]. Bug reports -containing patches should include the 'PATCH' keyword. - -Patches should be created using the unified diff form. - ie. svn diff file-to-be-patched.c > patch.diff +Patches should be submitted to github as pull requests: + https://github.com/mate-desktop/mate-control-center/pulls + https://help.github.com/articles/fork-a-repo + https://help.github.com/articles/using-pull-requests |