Re: git push hook to check for outdated timestamps

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: git push hook to check for outdated timestamps
Date: 2015-06-26 20:24:50
Message-ID: CA+TgmoYH-BB0OA27a+=on0SQT=AgX+P9XfwsdbJVpc+yVHOFwQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 26, 2015 at 4:11 PM, Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-06-26 21:12:41 Re: Removing SSL renegotiation (Was: Should we back-patch SSL renegotiation fixes?)
Previous Message Robert Haas 2015-06-26 20:23:28 open items list cleanup