Re: [HACKERS] show precise repos version for dev builds? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] show precise repos version for dev builds?
Date
Msg-id CA+TgmoZcoiLTudE-mj3smzyy4+QZovz6GDKAoZNuKPCQsoLYNA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] show precise repos version for dev builds?  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: [HACKERS] show precise repos version for dev builds?
Re: [HACKERS] show precise repos version for dev builds?
List pgsql-hackers
On Thu, Oct 12, 2017 at 4:50 PM, Fabien COELHO <coelho@cri.ensmp.fr> wrote:
> "svnversion" adds a "M" for modified on the status. There is an option with
> "git describe" to get something similar:
>
>     git describe --long --always --all --dirty

I tried this out a bit:

[rhaas pgsql]$ git describe --long --always --all --dirty
heads/master-0-gd133982d59
[rhaas pgsql]$ git checkout head~
...blah blah...
[rhaas pgsql]$ git describe --long --always --all --dirty
heads/x-218-g6393613b6a

Eh, what?  Hmm, maybe it's because I have a local branch called 'x'
lying around from something or other.

[rhaas pgsql]$ git branch -D x
Deleted branch x (was 77b6b5e9ce).
[rhaas pgsql]$ git describe --long --always --all --dirty
tags/REL_10_BETA3-458-g6393613b6a

Mmph.  I understand the desire to identify the exact commit used for a
build somehow, but something whose output depends on whether or not I
left a branch lying around locally doesn't seem that great.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Gourav Kumar
Date:
Subject: [HACKERS] Disable cross products in postgres
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] [PATCH] pageinspect function to decode infomasks