[cairo-commit] RELEASING

[Bryce Harrington]

 RELEASING |   10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

New commits:
commit 55e0b214ea13136acf4e234e620f637ee59e0924
Author: Bryce Harrington <bryce at osg.samsung.com>
Date:   Tue Dec 20 11:42:57 2016 -0800

    RELEASING: Fix tabbing

diff --git a/RELEASING b/RELEASING
index 0a824f0..424902e 100644
--- a/RELEASING
+++ b/RELEASING
@@ -2,10 +2,10 @@ Here are the steps to follow to create a new cairo release:
 
 1) Ensure that there are no local, uncommitted/unpushed mods.
 
-        You're probably in a good state if both "git diff
-        HEAD" and "git log master..origin/master" give no output.  Also make
-        sure you have libglib2.0-doc installed (else you'll get
-        excessive gtk-doc cross reference warnings in the next step).
+	You're probably in a good state if both "git diff
+	HEAD" and "git log master..origin/master" give no output.  Also make
+	sure you have libglib2.0-doc installed (else you'll get
+	excessive gtk-doc cross reference warnings in the next step).
 
 2) Verify that the code passes "make distcheck"
 
@@ -38,7 +38,7 @@ Here are the steps to follow to create a new cairo release:
 	suite passing, here's the magic env vars to set when doing
 	'make distcheck' and 'make release-publish' that will let you
 	get away with it.  At any cost, never ever release without
-	(implied) distchecking.  Every time we got around it, it turned
+	(implied) distchecking.	 Every time we got around it, it turned
 	out to be a disaster.  Anyway, here's the pass code:
 
 		DISPLAY= CAIRO_TEST_TARGET=" "