From: Junio C Hamano <junkio@cox.net>
To: lamikr@cc.jyu.fi
Cc: git@vger.kernel.org
Subject: Re: [ANNOUCNE] GIT 1.1.0
Date: Mon, 09 Jan 2006 16:28:03 -0800 [thread overview]
Message-ID: <7v7j99exkc.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <43C2F7E2.4090909@cc.jyu.fi> (lamikr@cc.jyu.fi's message of "Tue, 10 Jan 2006 01:55:14 +0200")
lamikr <lamikr@cc.jyu.fi> writes:
> Did you mean that things should work after 1.1.1 is released?
> I tried to fresh build and install of 1.1.0 on top of the previous
> 1.1.0 build but "git --version" is still displaying me "git version 1.0.GIT"
You need to build from a git repository for these automated
version numbers to work, and this will *not* change post 1.1.1.
But with the patch I sent out earlier, you should be able to:
$ VN=1.1.1 make
in a non-git repository (e.g. an untarred directory from a
tarball). What the patch fixes is to fix it for RPM binary
packages.
I expect that people building from the source do so from a git
repository not from a tarball, except when bootstrapping, so
hopefully this should not be too much of a problem.
next prev parent reply other threads:[~2006-01-10 0:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 1:20 [ANNOUCNE] GIT 1.1.0 Junio C Hamano
2006-01-09 8:49 ` Coywolf Qi Hunt
2006-01-09 9:41 ` Junio C Hamano
2006-01-09 10:38 ` Junio C Hamano
2006-01-09 11:09 ` Martin Langhoff
2006-01-11 9:25 ` Gerrit Pape
2006-01-09 20:43 ` lamikr
2006-01-09 22:22 ` Andreas Ericsson
2006-01-09 22:59 ` Junio C Hamano
2006-01-09 23:55 ` lamikr
2006-01-10 0:22 ` Andreas Ericsson
2006-01-10 1:21 ` Junio C Hamano
2006-01-10 14:49 ` Johannes Schindelin
2006-01-10 0:28 ` Junio C Hamano [this message]
2006-01-10 2:00 ` H. Peter Anvin
2006-01-10 3:05 ` 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=7v7j99exkc.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=lamikr@cc.jyu.fi \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).