diff options
author | Bryce Harrington <bryce@osg.samsung.com> | 2016-12-20 11:42:57 -0800 |
---|---|---|
committer | Bryce Harrington <bryce@osg.samsung.com> | 2016-12-20 11:42:57 -0800 |
commit | 55e0b214ea13136acf4e234e620f637ee59e0924 (patch) | |
tree | 3edc0022819cb96a10d9ae249cc29f19b01ac44f | |
parent | 3c5868a90ddf4a3a65bfe059bb7b4907b73e58c2 (diff) |
RELEASING: Fix tabbing
-rw-r--r-- | RELEASING | 10 |
1 files changed, 5 insertions, 5 deletions
@@ -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=" " |