From: Evan Martin <martine@danga.com>
Date: Fri, 5 Apr 2013 17:07:48 +0000 (-0700)
Subject: decided against using XXX in the manual for unknown versions
X-Git-Tag: v1.3.0~1^2~61
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=a87ffee6bb53ebdd68e29580d67cc4093100e82e;p=platform%2Fupstream%2Fninja.git

decided against using XXX in the manual for unknown versions
---

diff --git a/RELEASING b/RELEASING
index 0593e6d..3f83c7b 100644
--- a/RELEASING
+++ b/RELEASING
@@ -3,8 +3,7 @@ Notes to myself on all the steps to make for a Ninja release.
 1. git checkout release; git merge master
 2. fix version number in source (it will likely conflict in the above)
 3. fix version in doc/manual.asciidoc
-4. grep doc/manual.asciidoc for XXX, fix version references
-5. rebuild manual, put in place on website
-6. commit, tag, push
-7. construct release notes from prior notes
+4. rebuild manual, put in place on website
+5. commit, tag, push
+6. construct release notes from prior notes
    credits: git shortlog -s --no-merges REV..