summaryrefslogtreecommitdiff
path: root/libcmark-gfm/build/bootstrap.build
diff options
context:
space:
mode:
authorKaren Arutyunov <karen@codesynthesis.com>2019-06-22 19:45:25 +0300
committerKaren Arutyunov <karen@codesynthesis.com>2019-06-22 19:45:25 +0300
commit198fe549da3fce9f989f539b138867bdba6e7ede (patch)
tree273ed68a7d3a63fb8de495869cd42eb1e0c04890 /libcmark-gfm/build/bootstrap.build
parentaa2098530bba690957fd211ac51a05bb38c39512 (diff)
Release version 0.29.0-a.1+3v0.29.0-a.1+3
Bump toolchain version dependency to 0.11.0 in manifest. Switch to topics from tags in manifest. Add upstream-version value to manifest.
Diffstat (limited to 'libcmark-gfm/build/bootstrap.build')
-rw-r--r--libcmark-gfm/build/bootstrap.build3
1 files changed, 1 insertions, 2 deletions
diff --git a/libcmark-gfm/build/bootstrap.build b/libcmark-gfm/build/bootstrap.build
index 699205e..61fe373 100644
--- a/libcmark-gfm/build/bootstrap.build
+++ b/libcmark-gfm/build/bootstrap.build
@@ -30,8 +30,7 @@ using dist
# a more sensible versioning scheme (or if we decide to switch for some
# reason), we will multiply the first three upstream components by 100 and add
# <gfm-version> to one of them (always to patch for zero <major> but if/when
-# <major> becomes non-zero, we will have to decide based on the changes). We
-# also mention the upstream release in the package summary for information.
+# <major> becomes non-zero, we will have to decide based on the changes).
#
# Similar to upstream we use the <gfm-version> in the ABI version. When
# rebasing on upstream we should check SOVERSION definition in their