summaryrefslogtreecommitdiff
path: root/Mk
diff options
context:
space:
mode:
authorDirk Engling <erdgeist@erdgeist.org>2026-11-03 14:38:43 +0100
committerDirk Engling <erdgeist@erdgeist.org>2026-11-03 14:38:43 +0100
commit51f6ccc534df06446374c984ba61e892ee5a6c9a (patch)
tree89b68c6a7fef48bb26a5df259e7991571dc418a7 /Mk
parent33b5f6790db4e91ebd2370a97405e13932c4759c (diff)
I just noticed that we've already had a release v1.0.0, so we bump the version to 2.0.0
Diffstat (limited to 'Mk')
-rw-r--r--Mk/release.mk2
1 files changed, 1 insertions, 1 deletions
diff --git a/Mk/release.mk b/Mk/release.mk
index 5c4afe9..e5336e0 100644
--- a/Mk/release.mk
+++ b/Mk/release.mk
@@ -2,7 +2,7 @@
2# In a checkout it is absent and git answers instead. A release is always 2# In a checkout it is absent and git answers instead. A release is always
3# tagged, so in a tarball both of these are that tag, and the gitweb link 3# tagged, so in a tarball both of these are that tag, and the gitweb link
4# is to it. Between releases there is no tag and the version is the commit. 4# is to it. Between releases there is no tag and the version is the commit.
5VERSION=1.0.0 5VERSION=2.0.0
6 6
7TARBALL_VERSION=test -r .tarball-version && read v < .tarball-version && echo "$$v" 7TARBALL_VERSION=test -r .tarball-version && read v < .tarball-version && echo "$$v"
8HAVE_GIT=command -v git >/dev/null && test -d .git 8HAVE_GIT=command -v git >/dev/null && test -d .git