summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBryce Harrington <bryce@osg.samsung.com>2014-10-29 15:27:19 -0700
committerBryce Harrington <bryce@osg.samsung.com>2014-10-29 15:27:19 -0700
commitf7d0f80d2d880bea6b2fdbff579b21100355c1be (patch)
treee671b4d5f091477585185aebddd5e69db8c15f09
parentcaa4c9fdeb3aecd9a4288114e75d24ec931cd01b (diff)
downloadcairo-f7d0f80d2d880bea6b2fdbff579b21100355c1be.tar.gz
RELEASING: Be explicit as to which tag is pushed
-rw-r--r--RELEASING2
1 files changed, 1 insertions, 1 deletions
diff --git a/RELEASING b/RELEASING
index 235a90226..f6f5eeb51 100644
--- a/RELEASING
+++ b/RELEASING
@@ -113,7 +113,7 @@ Here are the steps to follow to create a new cairo release:
8) Push the newly created tag out to the central tree with a command
something like:
- git push --tags
+ git push upstream master X.Y.Z
9) Edit the cairo bugzilla product and add the new version numbers. Note
that you need to add two versions. One for the release/snapshot (with