From eb3c38e3adb8034513e8cf43202f5da39a6964be Mon Sep 17 00:00:00 2001 From: Elijah Newren Date: Sat, 1 Sep 2007 18:50:07 +0000 Subject: [PATCH] update; cvs->svn & mention GConf needed Make it match idiotic format 2007-09-01 Elijah Newren * HACKING: update; cvs->svn & mention GConf needed * MAINTAINERS: Make it match idiotic format requirements (I love you Olav!) svn path=/trunk/; revision=3317 --- ChangeLog | 6 ++++++ HACKING | 21 ++++++++++----------- MAINTAINERS | 12 +++++++++--- 3 files changed, 25 insertions(+), 14 deletions(-) diff --git a/ChangeLog b/ChangeLog index 9df500e28..0341dfddf 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2007-09-01 Elijah Newren + + * HACKING: update; cvs->svn & mention GConf needed + * MAINTAINERS: Make it match idiotic format requirements (I love + you Olav!) + 2007-08-07 Thomas Thurman * configure.in: post-release bump to 2.19.89. diff --git a/HACKING b/HACKING index d8b67211d..a6cbdf5e0 100644 --- a/HACKING +++ b/HACKING @@ -42,18 +42,17 @@ Minimal Building/Testing Environment build a development version of Metacity -- odds are, you may be able to build metacity from CVS without building any other modules. - As long as you have gtk+ >= 2.10 with your distro (gtk+ >= 2.6 if - you manually revert the change from bug 348633), you should be able - to install your distro's development packages (e.g. gtk2-devel, - GConf2-devel, startup-notification-devel on Fedora; also, remember - to install the gnome-common package which is needed for building cvs - versions of Gnome modules like Metacity) as well as the standard - development tools (gcc, autoconf, automake, pkg-config, intltool, - and libtool) and be ready to build and test Metacity. Steps to do - so: + As long as you have gtk+ >= 2.10 and GConf with your distro (gtk+ >= + 2.6 if you manually revert the change from bug 348633), you should + be able to install your distro's development packages + (e.g. gtk2-devel, GConf2-devel, startup-notification-devel on + Fedora; also, remember to install the gnome-common package which is + needed for building cvs versions of Gnome modules like Metacity) as + well as the standard development tools (gcc, autoconf, automake, + pkg-config, intltool, and libtool) and be ready to build and test + Metacity. Steps to do so: - $ cvs -q -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome \ - checkout metacity + $ svn checkout http://svn.gnome.org/svn/metacity/trunk metacity $ cd metacity $ ./autogen.sh --prefix /usr $ make diff --git a/MAINTAINERS b/MAINTAINERS index 72c9cc037..cc9e97ffb 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -1,13 +1,17 @@ Currently active maintainers -------------------------------- -Elijah Newren (newren gmail com) +Elijah Newren +Email: newren gmail com +Userid: newren - Usually won't touch the theme bugs (isn't interested) or the compositor (until open source nvidia drivers are up to snuff). Tends to be most interested in libwnck/gtk interactions, focus issues, constraints problems, and raising/stacking, but works on just about anything other than themes and the compositor. -Thomas Thurman (thomas thurman org uk) +Thomas Thurman +Email: thomas thurman org uk +Userid: tthurman - Responsible for all theme bugs and the compositor (thank goodness Thomas got involved, eh?). I'm sure he'll replace this sentence with his interests when he reads it. ;-) @@ -15,7 +19,9 @@ Thomas Thurman (thomas thurman org uk) Semi-active maintainers -------------------------------- -Havoc Pennington (hp redhat com) +Havoc Pennington +Email: hp redhat com +Userid: hp - Original author. Doesn't patch metacity anymore, but is active in answering questions, responding to bugs, providing very helpful suggestions and insight, and even assisting with debugging.