From: Martin Atukunda <matlads@dsmagic.com>
To: git@vger.kernel.org
Cc: Martin Atukunda <matlads@dsmagic.com>
Subject: [PATCH 1/2] Build GIT_VERSION from VERSION, PATCHLEVEL, and SUBLEVEL variables.
Date: Thu, 17 Nov 2005 16:25:37 +0300 [thread overview]
Message-ID: <11322339373013-git-send-email-matlads@dsmagic.com> (raw)
In-Reply-To: <11322339372137-git-send-email-matlads@dsmagic.com>
This will allow scripts to be able to determine which git release they
target (or require).
Signed-Off-By: Martin Atukunda <matlads@dsmagic.com>
---
Makefile | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)
applies-to: 1e3fcf60526c196a46433e6947c9104ca236f230
968e5b59fba66a1b146c643e5161978c787d4273
diff --git a/Makefile b/Makefile
index ebff990..74c6b9e 100644
--- a/Makefile
+++ b/Makefile
@@ -50,7 +50,11 @@
# 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 = 0.99.9.GIT
+VERSION = 0
+PATCHLEVEL = 99
+SUBLEVEL = 9
+EXTRAVERSION = GIT
+GIT_VERSION=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL).$(EXTRAVERSION)
# CFLAGS and LDFLAGS are for the users to override from the command line.
---
0.99.9.GIT
next prev parent reply other threads:[~2005-11-17 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 13:25 [PATCH] Add .git/version Martin Atukunda
2005-11-17 13:25 ` Martin Atukunda [this message]
2005-11-17 13:25 ` [PATCH 2/2] Make init-db record the version in $GIT_DIR/version when creating repo Martin Atukunda
2005-11-17 13:39 ` [PATCH] Add .git/version Johannes Schindelin
2005-11-17 15:16 ` Martin Atukunda
2005-11-17 15:38 ` Johannes Schindelin
2005-11-17 16:04 ` Josef Weidendorfer
2005-11-17 15:44 ` Josef Weidendorfer
2005-11-17 16:33 ` Andreas Ericsson
2005-11-17 16:41 ` Josef Weidendorfer
2005-11-17 19:08 ` Martin Atukunda
2005-11-17 19:18 ` [PATCH] Add .git/version (Take 2) Martin Atukunda
2005-11-17 19:25 ` [PATCH] Add .git/version Junio C Hamano
2005-11-17 19:35 ` Linus Torvalds
2005-11-17 23:41 ` Johannes Schindelin
2005-11-18 0:49 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11322339373013-git-send-email-matlads@dsmagic.com \
--to=matlads@dsmagic.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.