aboutsummaryrefslogtreecommitdiff
path: root/pixman/RELEASING
diff options
context:
space:
mode:
authormarha <marha@users.sourceforge.net>2011-02-23 07:34:10 +0000
committermarha <marha@users.sourceforge.net>2011-02-23 07:34:10 +0000
commite8d899178e9ebe174e6b4a53297d3dfced8003f0 (patch)
tree407c4e3c78b0cc28e95e7f607d02975e2155a46f /pixman/RELEASING
parentaa5b2e956fcc17b27d0f20ba7af65c52b34ef135 (diff)
parentfbb8c9a149047ccb27e749053c83acf94dedcbf9 (diff)
downloadvcxsrv-e8d899178e9ebe174e6b4a53297d3dfced8003f0.tar.gz
vcxsrv-e8d899178e9ebe174e6b4a53297d3dfced8003f0.tar.bz2
vcxsrv-e8d899178e9ebe174e6b4a53297d3dfced8003f0.zip
svn merge ^/branches/released .
Diffstat (limited to 'pixman/RELEASING')
-rw-r--r--pixman/RELEASING4
1 files changed, 2 insertions, 2 deletions
diff --git a/pixman/RELEASING b/pixman/RELEASING
index 0103eaec9..8644f2d8d 100644
--- a/pixman/RELEASING
+++ b/pixman/RELEASING
@@ -11,7 +11,7 @@ Here are the steps to follow to create a new pixman release:
git log master...origin (no output; note: *3* dots)
2) Increment pixman_(major|minor|micro) in configure.ac according to
- the directions in that file. Use git commit to record this.
+ the directions in that file.
3) Make sure that new version works, including
@@ -23,7 +23,7 @@ Here are the steps to follow to create a new pixman release:
- the cairo test suite hasn't gained any new failures compared
to last pixman version.
-4) Use "git commit" to record any changes made in step 3.
+4) Use "git commit" to record the changes made in step 2 and 3.
5) Generate and publish the tar files by running