Re: git push hook to check for outdated timestamps - Mailing list pgsql-hackers

From Robert Haas
Subject Re: git push hook to check for outdated timestamps
Date
Msg-id CA+TgmoYH-BB0OA27a+=on0SQT=AgX+P9XfwsdbJVpc+yVHOFwQ@mail.gmail.com
Whole thread Raw
In response to Re: git push hook to check for outdated timestamps  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Fri, Jun 26, 2015 at 4:11 PM, Peter Eisentraut <peter_e@gmx.net> 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 don't particularly think that having separate AuthorDate and
>> CommitterDate fields has any value.  At least, it doesn't to me.  But
>> a linear-looking commit history does have value to me.  Someone else
>> might have different priorities; those are mine.
>
> Sure, that's why Git is configurable to particular preferences.  But we
> don't have to force everyone to use Git in a nonstandard way.

I respect your opinion, but I think you are out-voted, unless some of
the people who previously favored this proposal have changed their
minds based on this discussion.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: open items list cleanup
Next
From: Tom Lane
Date:
Subject: Re: Removing SSL renegotiation (Was: Should we back-patch SSL renegotiation fixes?)