Skip to content

Conversation

linonetwo
Copy link
Contributor

This fixes the problem described in #1112

Otherwise, it will display version likes v0.33.0

@gklyne
Copy link
Contributor

gklyne commented Jul 3, 2019

That certainly seems to be the cause of the problem.

But I worry where this "fix" is going if git describe behaves differently on different systems (which criticism applies also to my previous fix). It feels like a lurking problem waiting to bite.

An online search wasn't massively helpful, but did turn up:

On my system, git rev-parse exits silently with status 0 in a got repo, or with "fatal: Not a git repository (or any of the parent directories): .git" and status 128 if not. There seems to be a little consensus behind appropriate git rev-parse in this way - I guess because it dosn't actually do much with the repo itself?

Copy link
Member

@kjetilk kjetilk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@linonetwo
Copy link
Contributor Author

@gklyne I thought it is fine, because many people on Windows will install "Git for Windows", which behaves just like in Linux. And I tested it in MacOS, it is the same as Linux. So it might be a good enough solution.

@jaxoncreed jaxoncreed merged commit 5729fe5 into nodeSolidServer:master Jul 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants