Update manual set of copyright files for 2017
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/60f1e514ad0db017bc583b0e15d056b777bd9626
Modified Files
--
doc/src/sgml/legal.sgml | 2 +-
src/interfaces/libpq/libpq.rc.in | 2 +-
2 files changed, 2 ins
Update copyright for 2017
Backpatch-through: certain files through 9.2
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/83a25a5209d93615e6d5f3eee4ef649853478498
Modified Files
--
COPYRIGHT | 2 +-
doc/src/sgml/legal.sgml | 4 ++--
2 fil
Magnus Hagander writes:
> On Tue, Jan 3, 2017 at 6:59 PM, Heikki Linnakangas wrote:
>> Ok. Now let's wait for the fallout from the reset. This is an interesting
>> experiment, we'll find out how many people are annoyed by a reset :-).
> Yeah, and how many had time to pull. It was only out there
On Tue, Jan 3, 2017 at 06:57:44PM +0100, Magnus Hagander wrote:
> 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.
>
>
>
> It seems bruce pushed a whole bunch of merge conflicts, and possibly more. I
> think h
On Tue, Jan 3, 2017 at 6:59 PM, Jim Nasby wrote:
> On 1/3/17 11:57 AM, Magnus Hagander wrote:
>
>> I've pushed a reset to the master repo. Working on the mirror now.
>>
>
> Please don't forget github. :)
>
> Handled, thanks for the reminder.
--
Magnus Hagander
Me: http://www.hagander.net/
W
On Tue, Jan 3, 2017 at 6:59 PM, Heikki Linnakangas wrote:
> On 01/03/2017 07:57 PM, Magnus Hagander wrote:
>
>> On Tue, Jan 3, 2017 at 6:54 PM, Heikki Linnakangas
>> wrote:
>>
>> On 01/03/2017 07:49 PM, Bruce Momjian wrote:
>>>
>>> On Tue, Jan 3, 2017 at 06:46:32PM +0100, Magnus Hagander wrote:
On 01/03/2017 07:57 PM, Magnus Hagander wrote:
On Tue, Jan 3, 2017 at 6:54 PM, Heikki Linnakangas wrote:
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
On 1/3/17 11:57 AM, Magnus Hagander wrote:
I've pushed a reset to the master repo. Working on the mirror now.
Please don't forget github. :)
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble!
On Tue, Jan 3, 2017 at 6:54 PM, Heikki Linnakangas wrote:
> 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
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
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 wor
Update copyright for 2017
Backpatch-through: certain files through 9.2
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/7090eed3b3e476d6ac20ba8e5f6e3914f18f9632
Modified Files
--
COPYRIGHT | 2 +-
doc/src/sgml/legal.sgml | 4 ++--
2 files chan
Sorry, this will be reverted and redone.
---
On Tue, Jan 3, 2017 at 05:38:05PM +, Bruce Momjian wrote:
> Update copyright for 2017
>
> Backpatch-through: certain files through 9.2
>
> Branch
> --
> REL9_2_STABLE
>
Update copyright for 2017
Backpatch-through: certain files through 9.2
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/19371e148207c33d15fded06a178d58d0781141d
Modified Files
--
COPYRIGHT |2 +-
configur
Update copyright for 2017
Backpatch-through: certain files through 9.2
Branch
--
REL9_6_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/344ae600ac036675d52afca9e8b363628d78d36d
Modified Files
--
COPYRIGHT | 2 +-
doc/src/sgml/legal.sgml | 6 +++---
2 f
Update copyright for 2017
Backpatch-through: certain files through 9.2
Branch
--
REL9_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/1dfe7f068121d15d59c85ecd936d154922e195d1
Modified Files
--
COPYRIGHT | 2 +-
doc/src/sgml/legal.sgml | 6 +++---
2 f
Update copyright for 2017
Backpatch-through: certain files through 9.2
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/e7c586e7b222b80c42de473468ce5e7e14bbca60
Modified Files
--
COPYRIGHT | 2 +-
doc/src/sgml/legal.sgml | 6 +++---
2 f
Update copyright for 2017
Backpatch-through: certain files through 9.2
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/92ade06b2cf3985a93f45edd10d4855dcc0bf26d
Modified Files
--
COPYRIGHT | 2 +-
doc/src/sgml/legal.sgml | 6 +++---
2 f
Disable prompting for passphrase while (re)loading SSL config files.
OpenSSL's default behavior when loading a passphrase-protected key file
is to open /dev/tty and demand the password from there. It was kinda
sorta okay to allow that to happen at server start, but really that was
never workable
Fix hot standby tests for sequence catalog change
From: Kuntal Ghosh
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/3d54c16c24d7fd73c9fdfa4b2f946899f7f85e58
Modified Files
--
src/test/regress/expected/hs_standby_allowed.out | 2 +-
src/test/regress/sql/
Remove bogus notice that older clients might not work with MD5 passwords.
That was written when we still had "crypt" authentication, and it was
referring to the fact that an older client might support "crypt"
authentication but not "md5". But we haven't supported "crypt" for years.
(As soon as we
Remove bogus notice that older clients might not work with MD5 passwords.
That was written when we still had "crypt" authentication, and it was
referring to the fact that an older client might support "crypt"
authentication but not "md5". But we haven't supported "crypt" for years.
(As soon as we
Remove bogus notice that older clients might not work with MD5 passwords.
That was written when we still had "crypt" authentication, and it was
referring to the fact that an older client might support "crypt"
authentication but not "md5". But we haven't supported "crypt" for years.
(As soon as we
Remove bogus notice that older clients might not work with MD5 passwords.
That was written when we still had "crypt" authentication, and it was
referring to the fact that an older client might support "crypt"
authentication but not "md5". But we haven't supported "crypt" for years.
(As soon as we
Remove bogus notice that older clients might not work with MD5 passwords.
That was written when we still had "crypt" authentication, and it was
referring to the fact that an older client might support "crypt"
authentication but not "md5". But we haven't supported "crypt" for years.
(As soon as we
Remove bogus notice that older clients might not work with MD5 passwords.
That was written when we still had "crypt" authentication, and it was
referring to the fact that an older client might support "crypt"
authentication but not "md5". But we haven't supported "crypt" for years.
(As soon as we
26 matches
Mail list logo
