| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Jeremy Schneider <schneider(at)ardentperf(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: show precise repos version for dev builds? |
| Date: | 2017-10-14 05:25:06 |
| Message-ID: | alpine.DEB.2.20.1710140721020.13834@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Robert,
> 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.
Indeed, the branch/tag search might have a little strange behavior.
Probably you would be more happy with just the commit (--always) & knowing
that it was changed (--dirty).
sh> git describe --always --dirty
b81eba6
sh> vi README
# edit
sh> git describe --always --dirty
b81eba6-dirty
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | legrand legrand | 2017-10-14 07:09:39 | Re: Continuous integration on Windows? |
| Previous Message | Justin Pryzby | 2017-10-14 03:57:32 | SIGSEGV in BRIN autosummarize |