This page is no longer maintained — Please continue to the home page at www.scala-lang.org

tools/get-scala-revision.bat is broken

3 replies
Eugene Burmako
Joined: 2011-09-17,
User offline. Last seen 42 years 45 weeks ago.
C:\Projects\Kepler>git describe HEAD --abbrev=7 --match dev
fatal: No names found, cannot describe anything
gkossakowski
Joined: 2010-03-11,
User offline. Last seen 33 weeks 5 days ago.
Re: tools/get-scala-revision.bat is broken
On 29 January 2012 16:05, Eugene Burmako <eugene.burmako@epfl.ch> wrote:
C:\Projects\Kepler>git describe HEAD --abbrev=7 --match dev
fatal: No names found, cannot describe anything

This hardly gives enough of information. For example, what's the output of 'git show dev' and 'git show HEAD'?

--
Grzegorz Kossakowski

Eugene Burmako
Joined: 2011-09-17,
User offline. Last seen 42 years 45 weeks ago.
Re: tools/get-scala-revision.bat is broken
C:\Projects\Kepler>git show dev
fatal: ambiguous argument 'dev': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions

C:\Projects\Kepler>git show HEAD
WARNING: terminal is not fully functional
commit dd7d854fa2 (HEAD, topic/reify)
Author: Eugene Burmako <xeno.by@gmail.com>
Date: 51 minutes ago
...
By the way, Unix script works finely, and it doesn't do any "git describe" at all. Maybe something has changed in our tags, and Windows script simply wasn't updated? And, yeh, the bug has been there for several weeks (don't remember the exact moment, when it started happening).
On 29 January 2012 17:35, Grzegorz Kossakowski <grzegorz.kossakowski@gmail.com> wrote:
On 29 January 2012 16:05, Eugene Burmako <eugene.burmako@epfl.ch> wrote:
C:\Projects\Kepler>git describe HEAD --abbrev=7 --match dev
fatal: No names found, cannot describe anything

This hardly gives enough of information. For example, what's the output of 'git show dev' and 'git show HEAD'?

--
Grzegorz Kossakowski


extempore
Joined: 2008-12-17,
User offline. Last seen 35 weeks 3 days ago.
Re: tools/get-scala-revision.bat is broken

I'd certainly like to switch to using git-describe directly (it only
does what it does because I was working around the unavailability of
git describe on older test machines) but I know the IDE depends on the
exact version string so it needs to be coordinated.

If we used git describe our version strings would now look (at least
in part) like this:

v2.10.0-M1-79-g0f75c10703

We could throw the date in there too.

So can it be

v2.10.0-M1-79-g0f75c10703-2012-01-29

?

Copyright © 2012 École Polytechnique Fédérale de Lausanne (EPFL), Lausanne, Switzerland