Update README files to refer to git

Update various README files to refer to git instead of svn.
Also discontinue ChangeLog files.

ChangeLog

@@ -1,3 +1,9 @@
+=== ChangeLog discontinued ===
+
+	With the move to git, GTK+ is switching from a ChangeLog file
+	to relying on commit messages to provide change history. Please
+	see README.commits for guidance on the expected message format.
+
 2009-03-29  Christian Persch  <chpe@gnome.org>
 
 	Bug 577224 – crash when setting new icon after setting icon in

HACKING

@@ -15,24 +15,24 @@ can be found here:
 
         http://developer.gnome.org
 
-including information about using Subversion with GNOME:
+Information about using git with GNOME can be found here:
 
-        http://developer.gnome.org/tools/svn.html
+        http://live.gnome.org/GitMigration
 
-In order to get SVN gtk+ installed on your system, you need to have
+In order to get GIT gtk+ installed on your system, you need to have
-the most recent SVN versions of glib, pango, and atk installed as well.
+the most recent GIT versions of glib, pango, and atk installed as well.
 The installation process of these libraries is similar to that of gtk+, but
 needs to be fulfilled prior to installation of gtk+.
 
-If at all possible, please use SVN to get the latest development version of
+If at all possible, please use GIT to get the latest development version of
-gtk+ and glib.  You can do the following to get glib and gtk+ from SVN:
+gtk+ and glib. You can do the following to get glib and gtk+ from GIT:
 
-        $ svn checkout http://svn.gnome.org/svn/glib/trunk glib
+        $ git clone git://git.gnome.org/glib
-        $ svn checkout http://svn.gnome.org/svn/pango/trunk pango
+        $ git clone git://git.gnome.org/pango
-        $ svn checkout http://svn.gnome.org/svn/atk/trunk atk
+        $ git clone git://git.gnome.org/atk
-        $ svn checkout http://svn.gnome.org/svn/gtk+/trunk gtk+
+        $ git clone git://git.gnome.org/gtk+
 
-To compile the SVN version of gtk+ on your system, you will need to take
+To compile the GIT version of gtk+ on your system, you will need to take
 several steps to setup the tree for compilation.  You can do all these
 steps at once by running:
 
@@ -53,7 +53,7 @@ Note that autogen.sh runs configure for you.  If you wish to pass
 options like `--prefix=/usr' to `configure' you can give those options
 to `autogen.sh' and they will be passed on to `configure'.
 
-For information about submitting patches and committing changes
+For information about submitting patches and pushing changes
-to SVN, see the `README' and `README.commits' files. In particular, 
+to GIT, see the `README' and `README.commits' files. In particular,
-don't, under any circumstances, commit anything to SVN before
+don't, under any circumstances, push anything to GIT before
 reading and understanding `README.commmits'.

README.commits

@@ -1,11 +1,11 @@
-GTK+ is part of the GNOME Subversion repository. At the current time, any
+GTK+ is part of the GNOME git repository. At the current time, any
 person with write access to the GNOME repository, can make changes to
 GTK+. This is a good thing, in that it encourages many people to work
 on GTK+, and progress can be made quickly. However, GTK+ is a fairly
 large and complicated package that many other things depend on, so to
 avoid unnecessary breakage, and to take advantage of the knowledge
 about GTK+ that has been built up over the last 4 years, we'd like
-to ask people commiting to GTK+ to follow a few rules:
+to ask people committing to GTK+ to follow a few rules:
 
 0) Ask first. If your changes are major, or could possibly break existing
    code, you should always ask. If your change is minor and you've
@@ -25,30 +25,48 @@ to ask people commiting to GTK+ to follow a few rules:
 
 1) Ask _first_.
 
-2) There must be a ChangeLog for every commit. (If you discover that
+2) With git, we no longer maintain a ChangeLog file, but you are expected
-   you only committed half the files you meant to and need to fix that
+   to produce a meaningful commit message. Changes without a sufficient
-   up, or something, you don't need a new ChangeLog entry. But in general,
+   commit message will be reverted. See below for the expected format
-   ChangeLog entries are mandatory.) Changes without ChangeLog entries
+   of commit messages.
-   will be reverted.
-
-3) There _must_ be a ChangeLog for every commit.
 
 Notes:
 
-* If you are going to be changing many files in an experimental fashion,
+* When developing larger features or complicated bug fixes, it is
-  it probably is a good idea to create a separate branch for your changes.
+  advisable to work in a branch in your own cloned GTK+ repository.
+  You may even consider making your repository publically available
+  so that others can easily test and review your changes.
 
-* The ChangeLog entries should preferably match in date format
+* The expected format for git commit messages is as follows:
-  with the existing entries. You can set how emacs does this
-  by using customize mode:
 
-  - M-x customize
+=== begin example commit ===
-  - set Programming/Tools/ChangeLog/Add Log Time Format to
+Short explanation of the commit
-    'Old Format'
+
+Longer explanation explaining exactly what's changed, whether any
+external or private interfaces changed, what bugs were fixed (with bug
+tracker reference if applicable) and so forth. Be concise but not too brief.
+=== end example commit ===
+
+  - Always add a brief description of the commit to the _first_ line of
+    the commit and terminate by two newlines (it will work without the
+    second newline, but that is not nice for the interfaces).
+
+  - First line (the brief description) must only be one sentence and
+    should start with a capital letter unless it starts with a lowercase
+    symbol or identifier. Don't use a trailing period either. Don't exceed
+    72 characters.
+
+  - The main description (the body) is normal prose and should use normal
+    punctuation and capital letters where appropriate. Normally, for patches
+    sent to a mailing list it's copied from there.
+
+  - When committing code on behalf of others use the --author option, e.g.
+    git commit -a --author "Joe Coder <joe@coder.org>" and --signoff.
 
- Or, set the add-log-time-format to 'current-time-string in
- your .emacs file.
 
 Owen Taylor
 13 Aug 1998
 17 Apr 2001
+
+Matthias Clasen
+31 Mar 2009

contrib/gdk-pixbuf-xlib/ChangeLog

@@ -1,3 +1,9 @@
+=== ChangeLog discontinued ===
+
+	With the move to git, GTK+ is switching from a ChangeLog file
+	to relying on commit messages to provide change history. Please
+	see README.commits for guidance on the expected message format.
+
 2009-03-13  Matthias Clasen  <mclasen@redhat.com>
 
 	* === Released 2.16.0 ===

docs/reference/ChangeLog

@@ -1,3 +1,9 @@
+=== ChangeLog discontinued ===
+
+	With the move to git, GTK+ is switching from a ChangeLog file
+	to relying on commit messages to provide change history. Please
+	see README.commits for guidance on the expected message format.
+
 2009-03-25   Paul Bolle <pebolle@tiscali.nl>
 
 	Bug 562863 - GtkVscrollbar is hardly documented

gdk-pixbuf/ChangeLog

@@ -1,3 +1,9 @@
+=== ChangeLog discontinued ===
+
+	With the move to git, GTK+ is switching from a ChangeLog file
+	to relying on commit messages to provide change history. Please
+	see README.commits for guidance on the expected message format.
+
 2009-03-13  Matthias Clasen  <mclasen@redhat.com>
 
 	* === Released 2.16.0 ===

modules/engines/pixbuf/ChangeLog

@@ -1,3 +1,9 @@
+=== ChangeLog discontinued ===
+
+	With the move to git, GTK+ is switching from a ChangeLog file
+	to relying on commit messages to provide change history. Please
+	see README.commits for guidance on the expected message format.
+
 2009-03-13  Matthias Clasen  <mclasen@redhat.com>
 
 	* === Released 2.16.0 ===

modules/other/gail/ChangeLog

@@ -1,3 +1,9 @@
+=== ChangeLog discontinued ===
+
+	With the move to git, GTK+ is switching from a ChangeLog file
+	to relying on commit messages to provide change history. Please
+	see README.commits for guidance on the expected message format.
+
 2009-03-25  Tor Lillqvist  <tml@novell.com>
 
 	Bug 575644 - Cygwin gail build patch

po-properties/ChangeLog

@@ -1,3 +1,9 @@
+=== ChangeLog discontinued ===
+
+	With the move to git, GTK+ is switching from a ChangeLog file
+	to relying on commit messages to provide change history. Please
+	see README.commits for guidance on the expected message format.
+
 2009-03-30  Manoj Kumar Giri  <mgiri@redhat.com>
 
 	* or.po:  Updated Oriya Translation

po/ChangeLog

@@ -1,3 +1,9 @@
+=== ChangeLog discontinued ===
+
+	With the move to git, GTK+ is switching from a ChangeLog file
+	to relying on commit messages to provide change history. Please
+	see README.commits for guidance on the expected message format.
+
 2009-03-28  Jorge Gonzalez  <jorgegonz@svn.gnome.org>
 
 	* es.po: Fixed wrong string.