On Sat, Oct 14, 2017 at 4:47 AM, Robert Haas <robertmh...@gmail.com> wrote: > 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.
Similarly to Peter, I prefer a minimum amount of information so I tend to just use `git rev-parse --short HEAD` with --extra-version for my own builds. Looking at the timestamp of the files installed is enough to know when you worked on them, and when testing a patch and committing it on a local branch before compiling you can know easily where you left things off. git branch --contains is also useful to get from which branch is commit from. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
