summaryrefslogtreecommitdiff
path: root/autogen.sh
diff options
context:
space:
mode:
authorEmmanuele Bassi <ebassi@gnome.org>2015-01-03 20:34:20 +0000
committerEmmanuele Bassi <ebassi@gnome.org>2015-01-03 20:34:20 +0000
commit77ec8774a08c884d8acdf6c5f36a3e5003596626 (patch)
treea1ebb161dd9d46d9df5545db0dbbcd2727747e68 /autogen.sh
parentc3c89332f6541848b5c3853858249e39b116b4fd (diff)
downloadclutter-77ec8774a08c884d8acdf6c5f36a3e5003596626.tar.gz
WARNING: Massive revert commit
Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
Diffstat (limited to 'autogen.sh')
-rwxr-xr-xautogen.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/autogen.sh b/autogen.sh
index 5e195603a..61c3b46f5 100755
--- a/autogen.sh
+++ b/autogen.sh
@@ -18,7 +18,7 @@ test $TEST_TYPE $FILE || {
# GNU gettext automake support doesn't get along with git.
# https://bugzilla.gnome.org/show_bug.cgi?id=661128
-touch -t 200001010000 po/clutter-2.0.pot
+touch -t 200001010000 po/clutter-1.0.pot
GTKDOCIZE=`which gtkdocize`
if test -z $GTKDOCIZE; then