Re: pgsql: Update copyright for 2017

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Update copyright for 2017
Date: 2017-01-04 15:05:10
Message-ID: 21837.1483542310@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2017-01-03 13:02:28 -0500, Bruce Momjian wrote:
>> Yeah, I was doing parallel pulls of different branches in git via shell
>> script, and it seems the size of this commit showed me that doesn't
>> work. Sorry.

> Shouldn't you check the results of something like this before pushing?
> Sorry for piling on, but that seems like a quite critical step.

Actually, my takeaway from this was "don't ever use git reset on the repo".
"git revert" would have been much safer. Yeah, it would have meant that
git blame on the 9.2 branch would have some useless noise, but how much
does anyone still care about that?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Stephen Frost 2017-01-04 15:08:18 Re: pgsql: Update copyright for 2017
Previous Message Peter Eisentraut 2017-01-04 13:52:59 pgsql: Better fix for sequence access in hot standby test

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2017-01-04 15:05:13 Re: UNDO and in-place update
Previous Message web+postgresql 2017-01-04 15:03:01 BUG #14486: Inserting and selecting interval have different constraints