summaryrefslogtreecommitdiff
path: root/Makefile
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2005-12-22 06:33:37 (GMT)
committerJunio C Hamano <junkio@cox.net>2005-12-22 06:33:37 (GMT)
commitc894168631e4b7da66ed3993a4c92380d38599a8 (patch)
tree39a70bec4fc08119b0c65d32a37c6345db43d156 /Makefile
parent2a212746f44f18695d33931039da10f842de7b25 (diff)
downloadgit-c894168631e4b7da66ed3993a4c92380d38599a8.zip
git-c894168631e4b7da66ed3993a4c92380d38599a8.tar.gz
git-c894168631e4b7da66ed3993a4c92380d38599a8.tar.bz2
Versioning scheme changes.
HPA suggests it is simply silly to imitate Linux versioning scheme where the leading "2" does not mean anything anymore, and I tend to agree. The first feature release after 1.0.0 will be 1.1.0, and the development path leading to 1.1.0 will carry 1.0.GIT as the version number from now on. Similarly, the third maintenance release that follows 1.0.0 will not be 1.0.0c as planned, but will be called 1.0.3. The "maint" branch will merge in fixes and immediately tagged, so there is no need for 1.0.2.GIT that is in between 1.0.2 (aka 1.0.0b) and 1.0.3. Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Makefile')
-rw-r--r--Makefile2
1 files changed, 1 insertions, 1 deletions
diff --git a/Makefile b/Makefile
index 782cff9..88b89f9 100644
--- a/Makefile
+++ b/Makefile
@@ -55,7 +55,7 @@ all:
# Define USE_STDEV below if you want git to care about the underlying device
# change being considered an inode change from the update-cache perspective.
-GIT_VERSION = 1.0.0.GIT
+GIT_VERSION = 1.0.GIT
# CFLAGS and LDFLAGS are for the users to override from the command line.