RELEASING: Fix the step numbering

v2: Really fix the numbering (Emil Velikov)

Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>

1 files changed, 6 insertions, 6 deletions

diff --git a/RELEASING b/RELEASING
index e17dbea2..203b88bb 100644
--- a/RELEASING
+++ b/RELEASING
@@ -13,14 +13,14 @@ Follow these steps to release a new version of libdrm:
      modifications. You're probably in a good state if both "git diff
      HEAD" and "git log master..origin/master" give no output.
 
-  3) Bump the version number in configure.ac. We seem to have settled
+  2) Bump the version number in configure.ac. We seem to have settled
      for 2.4.x as the versioning scheme for libdrm, so just bump the
      micro version.
 
-  4) Run autoconf and then re-run ./configure so the build system
+  3) Run autoconf and then re-run ./configure so the build system
      picks up the new version number.
 
-  5) (optional step, release.sh will make distcheck for you, but it can be
+  4) (optional step, release.sh will make distcheck for you, but it can be
       heart warming to verify that make distcheck passes)
 
      Verify that the code passes "make distcheck".  Running "make
@@ -36,20 +36,20 @@ Follow these steps to release a new version of libdrm:
      Make sure that the version number reported by distcheck and in
      the tarball names matches the number you bumped to in configure.ac.
 
-  6) Commit the configure.ac change and make an annotated tag for that
+  5) Commit the configure.ac change and make an annotated tag for that
      commit with the version number of the release as the name and a
      message of "libdrm X.Y.Z".  For example, for the 2.4.16 release
      the command is:
 
 	git tag -a 2.4.16 -m "libdrm 2.4.16"
 
-  7) Push the commit and tag by saying
+  6) Push the commit and tag by saying
 
 	git push --tags origin master
 
      assuming the remote for the upstream libdrm repo is called origin.
 
-  6) Use the release.sh script from the xorg/util/modular repo to
+  7) Use the release.sh script from the xorg/util/modular repo to
      upload the tarballs to the freedesktop.org download area and
      create an annouce email template.  The script takes one argument:
      the path to the libdrm checkout. So, if a checkout of modular is