Re: pgsql: Update copyright for 2017

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, 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-04-18 14:28:36
Message-ID: CAD21AoB9OvDS3Mw2x2i=5RdMj=OHeeKb3WSuw-bqt1rSQnEqFQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Sat, Jan 7, 2017 at 1:14 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Wed, Jan 4, 2017 at 10:05:10AM -0500, Tom Lane wrote:
>> 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?
>
> FYI, my takeaway is that you can't run parallel 'git pull' operations on
> different branches checked out of the same tree, at least as setup from
> instructions on our wiki. Such parallel operations generate messages
> indicating someone else is working on the tree, but I now realize those
> are _warnings_ and this behavior should be avoided. Normally it works
> fine, but for a big commit, it can move a changeset from one branch to
> another, with disastrous consequences.
>
> Yes, I should have checked more, but I often do a pull before a push as
> another check, so that can mess it up too. Basically, if your tools are
> being used improperly, checking can make things worse too.
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + As you are, so once was I. As I am, so you will be. +
> + Ancient Roman grave inscription +
>
>
> --
> Sent via pgsql-committers mailing list (pgsql-committers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-committers

Hi,

During reading source code, I noticed that updating copyright for 2017
has been missing in some files. Attached patch fixes it.

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachment Content-Type Size
update_copyright.patch application/octet-stream 1.6 KB

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2017-04-18 14:39:09 pgsql: Also fix comment in sample postgresql.conf file, for "scram-sha-
Previous Message Andrew Dunstan 2017-04-18 12:54:07 pgsql: Simplify docs on creating a self-signed SSL certificate

Browse pgsql-hackers by date

  From Date Subject
Next Message Remi Colinet 2017-04-18 14:39:15 Re: [PATCH] New command to monitor progression of long running queries
Previous Message Peter Eisentraut 2017-04-18 14:24:05 Re: Logical replication launcher uses wal_retrieve_retry_interval