Re: [COMMITTERS] pgsql: Remove Christof Petig copyright on include

Поиск
Список
Период
Сортировка
От Jan Wieck
Тема Re: [COMMITTERS] pgsql: Remove Christof Petig copyright on include
Дата
Msg-id 4411B094.6030201@Yahoo.com
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Remove Christof Petig copyright on include file,  (Bruce Momjian <pgman@candle.pha.pa.us>)
Список pgsql-hackers
On 3/10/2006 10:53 AM, Bruce Momjian wrote:

> Jan Wieck wrote:
>> On 3/8/2006 5:31 PM, Bruce Momjian wrote:
>> > Alvaro Herrera wrote:
>> >> Bruce Momjian wrote:
>> >> > Log Message:
>> >> > -----------
>> >> > Remove Christof Petig copyright on include file, per author request.
>> >> 
>> >> Huh, I thought what he actually told was that the file was released
>> >> under BSD license.  Maybe I missed it, but I didn't see him asking to
>> >> remove the copyright.
>> >> 
>> >> We certainly have copyrights attributed to individual people.  Jan Wieck
>> >> has his name on the PL/Tcl and PL/pgSQL files, for example.
>> > 
>> > We should not have individual copyrights to individuals in our source
>> > tree.  If Jan's is in there, it should be removed too (with his
>> > approval).  The only copyright holder should be PostgreSQL Global
>> > Development Group.
>> > 
>> > Jan, would you fix that?
>> 
>> We've been there before, and not only once. I wonder why we still find 
>> more of these, because every time it comes up I agree to removal of it.
> 
> Perhaps your name reproduces somehow.  :-)

Scary to see it plastered all over the place.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #


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

Предыдущее
От: "Zeugswetter Andreas DCP SD"
Дата:
Сообщение: Re: problem with large maintenance_work_mem settings and
Следующее
От: Tom Lane
Дата:
Сообщение: Re: problem with large maintenance_work_mem settings and