From: Simon McVittie <simon.mcvittie@collabora.co.uk>
Date: Thu, 24 Feb 2011 15:43:24 +0000 (+0000)
Subject: Rename configure.in to configure.ac
X-Git-Tag: dbus-1.4.8~14^2~4^2~14
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ff04d7397a5cdfb41c8963d8f0d080529a6b1689;p=thirdparty%2Fdbus.git

Rename configure.in to configure.ac

Bug: https://bugs.freedesktop.org/show_bug.cgi?id=32245
---

diff --git a/HACKING b/HACKING
index 4a561f2bd..7a5a792c7 100644
--- a/HACKING
+++ b/HACKING
@@ -172,14 +172,14 @@ To make a release of D-Bus, do the following:
    then simply created an unsigned annotated tag:
    "git tag -a -m 'Released X.Y.Z' dbus-X.Y.Z".
 
- - bump the version number up in configure.in (so the micro version is odd),
+ - bump the version number up in configure.ac (so the micro version is odd),
    and commit it.  Make sure you do this *after* tagging the previous
    release! The idea is that git has a newer version number
    than anything released.
 
  - merge the branch you've released to the chronologically-later
    branch (usually "master"). You'll probably have to fix a merge
-   conflict in configure.in (the version number).
+   conflict in configure.ac (the version number).
 
  - push your changes and the tag to the central repository with
      git push origin master dbus-X.Y dbus-X.Y.Z
diff --git a/configure.in b/configure.ac
similarity index 100%
rename from configure.in
rename to configure.ac