aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@g5.osdl.org>2005-07-15 16:08:01 -0700
committerLinus Torvalds <torvalds@g5.osdl.org>2005-07-15 16:08:01 -0700
commit78d9d414123ad6f4f522ffecbcd9e4a7562948fd (patch)
tree04c102266a3afad1444f74030320d33ba7cff437
parent71931c19658bd99747ebbb93f0155384ba97df2c (diff)
downloadgit-78d9d414123ad6f4f522ffecbcd9e4a7562948fd.tar.gz
git-78d9d414123ad6f4f522ffecbcd9e4a7562948fd.tar.xz
Ahh, the heady days of 0.99 patchfilesv0.99.1
Now, not all projects can be as refined as Linux. Before the final 1.0 release, we went through fifteen 0.99 patchfiles, and pl14 alone went through subreleases 'a' through 'z'. Now _that_ is a release process. Not to mention the odd-ball releases, like 0.96c+ Sadly, in this day and age of RPM's etc, we have silly limitations, and I cannot call this release '0.99pl5a or some such awe-inspiring name just because "rpmbuild" is such a party pooper. So it's just 0.99.1. Oh well. Aspiring to such greatness as the Linux release numbering is hubris anyway. You can attain such perfection only once in your life.
-rw-r--r--Makefile4
1 files changed, 2 insertions, 2 deletions
diff --git a/Makefile b/Makefile
index dd3c6ccb6..8492b0857 100644
--- a/Makefile
+++ b/Makefile
@@ -9,7 +9,7 @@
# BREAK YOUR LOCAL DIFFS! show-diff and anything using it will likely randomly
# break unless your underlying filesystem supports those sub-second times
# (my ext3 doesn't).
-GIT_VERSION=0.99
+GIT_VERSION=0.99.1
COPTS=-O2
CFLAGS=-g $(COPTS) -Wall
@@ -174,7 +174,7 @@ diffcore-break.o : $(LIB_H) diffcore.h
diffcore-order.o : $(LIB_H) diffcore.h
epoch.o: $(LIB_H)
-git-core.spec: git-core.spec.in
+git-core.spec: git-core.spec.in Makefile
sed -e 's/@@VERSION@@/$(GIT_VERSION)/g' < $< > $@
GIT_TARNAME=git-core-$(GIT_VERSION)