Re: pgsql: Update copyright for 2017

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Update copyright for 2017
Date: 2017-01-03 17:54:37
Message-ID: 6fe16c90-0987-00a1-804d-587e193f2574@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 01/03/2017 07:49 PM, Bruce Momjian wrote:
> On Tue, Jan 3, 2017 at 06:46:32PM +0100, Magnus Hagander wrote:
>> Is this a big enough boo that we actually want to reset the master repo to get
>> rid of it?
>>
>> If so, we need to do it *now* beore people get a chance to mirror it properly..
>>
>> Thoughts?
>>
>> If not, just a revert should work of course..
>
> OK, not sure how this happened but I think it has to do with my
> accidentally doing a 'pull' after the changes, and doing multiple
> branches.
>
> Whatever you suggest is fine --- I will wait.

I'm leaning for +1 for resetting. It'll be a pain for any mirrors of the
repo, but I think the clean history is worth it.

- Heikki

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Magnus Hagander 2017-01-03 17:57:44 Re: pgsql: Update copyright for 2017
Previous Message Bruce Momjian 2017-01-03 17:49:14 Re: [COMMITTERS] pgsql: Update copyright for 2017

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2017-01-03 17:57:27 Re: proposal: session server side variables
Previous Message Fabien COELHO 2017-01-03 17:52:34 Re: proposal: session server side variables