summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorSimon McVittie <simon.mcvittie@collabora.co.uk>2011-02-24 15:43:24 +0000
committerSimon McVittie <simon.mcvittie@collabora.co.uk>2011-02-24 15:43:24 +0000
commitff04d7397a5cdfb41c8963d8f0d080529a6b1689 (patch)
tree10cd11f404521ce8c31bb2652556bc436fe0d7bc /HACKING
parentcf33a006dc3324a0a680454f76fc0648a9f562a1 (diff)
Rename configure.in to configure.ac
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=32245
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING4
1 files changed, 2 insertions, 2 deletions
diff --git a/HACKING b/HACKING
index 4a561f2b..7a5a792c 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