Re: git push hook to check for outdated timestamps

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: git push hook to check for outdated timestamps
Date: 2015-07-14 18:19:12
Message-ID: 55A552A0.1080503@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/14/15 3:44 AM, Alvaro Herrera wrote:
> Peter Eisentraut wrote:
>> On 6/25/15 8:08 PM, Robert Haas wrote:
>>> Because I don't want to have to do git log --format=fuller to see when
>>> the thing was committed, basically.
>>
>> Then I suggest to you the following configuration settings:
>>
>> [format]
>> pretty=cmedium
>> [pretty]
>> cmedium="format:%C(auto,yellow)commit %H%C(reset)%nCommit: %cn <%ce>%nCommitDate: %cd%n%n%w(80,4,4)%B"
>
> I have been using a slightly tweaked version of this and I have found
> that the %w(80,4,4)%B thingy results in mangled formatting;

I have since refined this to

... %n%n%w(0,4,4)%s%n%+b

You might find that that works better.

One of the curiosities is that the built-in log formats don't appear to
be defined or easily definable in terms of the formatting language.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-07-14 18:30:17 Re: git push hook to check for outdated timestamps
Previous Message Sawada Masahiko 2015-07-14 18:07:50 Re: Freeze avoidance of very large table.