aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarek Olšák2018-02-17 13:25:02 -0600
committerMarek Olšák2018-02-17 13:25:02 -0600
commite87a87925ea23e84ed6f67de73a5ef2713ca2c49 (patch)
tree863e178cc25f334a5c35db14a33be5b22c747040
parenta05f5ac3023fd9a16b0dfffe30786e83c7513197 (diff)
downloadexternal-libgbm-e87a87925ea23e84ed6f67de73a5ef2713ca2c49.tar.gz
external-libgbm-e87a87925ea23e84ed6f67de73a5ef2713ca2c49.tar.xz
external-libgbm-e87a87925ea23e84ed6f67de73a5ef2713ca2c49.zip
RELEASING: mention meson
-rw-r--r--RELEASING6
1 files changed, 3 insertions, 3 deletions
diff --git a/RELEASING b/RELEASING
index 262ca08d..7e03e3b9 100644
--- a/RELEASING
+++ b/RELEASING
@@ -9,9 +9,9 @@ However, this is up to whoever is driving the feature in question.
9 9
10Follow these steps to release a new version of libdrm: 10Follow these steps to release a new version of libdrm:
11 11
12 1) Bump the version number in configure.ac. We seem to have settled 12 1) Bump the version number in configure.ac and meson.build. We seem
13 for 2.4.x as the versioning scheme for libdrm, so just bump the 13 to have settled for 2.4.x as the versioning scheme for libdrm, so
14 micro version. 14 just bump the micro version.
15 15
16 2) Run autoconf and then re-run ./configure so the build system 16 2) Run autoconf and then re-run ./configure so the build system
17 picks up the new version number. 17 picks up the new version number.