From 2ebc394a1ae159238254696fe0cb487528ee239b Mon Sep 17 00:00:00 2001 From: Stefano Karapetsas Date: Sat, 27 Oct 2012 16:44:58 +0200 Subject: update README --- README | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) diff --git a/README b/README index 040b236e..36e153c6 100644 --- a/README +++ b/README @@ -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 -matecc-list@gnome.org 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 -- cgit v1.2.1