SVN commit 987575 by dfaure:

as discussed with thiago:

It is recommended to use kde-qt.git instead of qt-copy. Right now both are possible,
but please transition at some point so that we can get rid of qt-copy later.
Also, adding new patches in qt-copy now requires using kde-qt.git anyway.

CCMAIL: kde-core-devel@kde.org


 M  +17 -19    README.qt-copy  


--- trunk/qt-copy/README.qt-copy #987574:987575
@@ -2,6 +2,18 @@
 modifications which are necessary for KDE; these are listed in the
 patches directory.
 
+0. Switching to git
+===================
+
+It is recommended to use kde-qt.git instead of qt-copy. Right now both are possible,
+but please transition at some point so that we can get rid of qt-copy later.
+Also, adding new patches in qt-copy now requires using kde-qt.git anyway.
+
+How to get kde-qt:
+  git clone git://gitorious.org/+kde-developers/qt/kde-qt.git
+
+Then read README.kde-qt and forget about the rest of this README.qt-copy here :-)
+
 1. Qt-copy patches
 ==================
 
@@ -141,28 +153,14 @@
 be accounted for.
 
 To create a patch, do the following:
-  a) make sure your Qt sources are clean of other changes. Run:
-     svn revert -R .
-  b) make your changes to the Qt source code and verify that it
-  compiles, links and works.
-  c) open the patches/README file and get the next patch number
-  (you must read and understand the README file; if you don't, ask for
-  help from other KDE developers)
-  d) create the patch with:
-     svn diff > patches/NNNN-short-description-of-your-patch.diff
-  where NNNN is the next available number.
-  e) open the file you've just created and add the header to it. The
+  a) see section 0 about checking out kde-qt.git
+  b) follow the instructions in kde-qt.git about making patches and submitting them
+  c) save the patch here for qt-copy users under the patches subdir, using the same
+     name as your git branch.
+  d) open the file you've just created and add the header to it. The
   header should be the template in patches/README followed by a longer
   description of your patch.
 
-Don't forget to submit your patch to qt-bugs@trolltech.com along with
-the long description of the issue found, if you haven't already.
-Qt Software does not monitor the patches/ directory, so qt-copy
-patches do not get automatically applied to Qt official releases.
-
-When you receive the issue number and task tracker numbers, update the
-patch file.
-
 9. Known issues with current Qt code
 ====================================