Re: pg_rewind, a tool for resynchronizing an old master after failover

Поиск
Список
Период
Сортировка
От Christophe Pettus
Тема Re: pg_rewind, a tool for resynchronizing an old master after failover
Дата
Msg-id B7E002E4-3B38-4BDA-A2FC-5B6D4B1D253D@thebuild.com
обсуждение исходный текст
Ответ на Re: pg_rewind, a tool for resynchronizing an old master after failover  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
On May 28, 2013, at 12:49 PM, Alvaro Herrera wrote:

> We've had request from companies because they wanted to distribute
> Postgres and lawyers weren't comfortable with copyright statements in
> assorted files.  In those cases we've asked the people mentioned in such
> copyright statements, got approval to remove the offending copyright
> lines, and removed them.

I assume this topic has come up and been rejected for some reason, but just in case: The Django project requires an
explicitagreement for contributions that end up in the main source tree for it, part of which is the acceptance of the
Djangolicense and copyright notice.  (I don't have my copy right in front of me, but I don't think it's a full-on
assignmentof copyright.) 

--
-- Christophe Pettus  xof@thebuild.com




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: pg_rewind, a tool for resynchronizing an old master after failover
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: pg_rewind, a tool for resynchronizing an old master after failover