From: Andreas Ericsson <ae@op5.se>
To: lamikr@cc.jyu.fi
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [ANNOUCNE] GIT 1.1.0
Date: Tue, 10 Jan 2006 01:22:34 +0100 [thread overview]
Message-ID: <43C2FE4A.50203@op5.se> (raw)
In-Reply-To: <43C2F7E2.4090909@cc.jyu.fi>
lamikr wrote:
>>Ah, sorry, and thanks for catching this. RPM building procedure
>>is somewhat tricky, and I failed to catch this bug. Fixed in my
>>tree --- this calls for an early 1.1.1 release I guess.
>>
>>On the other hand, if you are building from the source, what
>>Andreas said applies, and in addition you need to fetch v1.1.0
>>tag before building; otherwise the versioning mechanism would not
>>notice you are building v1.1.0.
>>
>>
>
> I was not using git for fetching git sources,
> I have build from the git 1.1.0.tar.bz2.
>
> Did you mean that things should work after 1.1.1 is released?
Not unless you build from the git-repo, no.
Snapshots will fail to set the "proper" version every time, because the
GIT-VERSION-FILE: is a forced target and even if git-describe is present
it will find neither tags nor HEAD.
I have no solution to this, apart from rewriting the Makefile on the fly
whenever a release tarball is created.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2006-01-10 0:22 UTC|newest]
Thread overview: 17+ 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-10 22:15 ` Norbert Tretkowski
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 [this message]
2006-01-10 1:21 ` Junio C Hamano
2006-01-10 14:49 ` Johannes Schindelin
2006-01-10 0:28 ` Junio C Hamano
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=43C2FE4A.50203@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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 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.