Re: Pgfoundry and gborg: shut one down

Поиск
Список
Период
Сортировка
От Marc G. Fournier
Тема Re: Pgfoundry and gborg: shut one down
Дата
Msg-id 20060222131121.G1931@ganymede.hub.org
обсуждение исходный текст
Ответ на Re: Pgfoundry and gborg: shut one down  ("Jim C. Nasby" <jnasby@pervasive.com>)
Ответы Re: Pgfoundry and gborg: shut one down  ("Jim C. Nasby" <jnasby@pervasive.com>)
Список pgsql-hackers
On Wed, 22 Feb 2006, Jim C. Nasby wrote:

> On Mon, Feb 20, 2006 at 02:49:30PM +0700, Jeroen T. Vermeulen wrote:
>> On Mon, February 20, 2006 11:00, Marc G. Fournier wrote:
>>
>>>> Speaking for libpqxx, my only concern with that is the mailing list.
>>>> Would those have to move to different addresses--or conversely, would a
>>>> forced migration make it much easier to move *all* GBorg mailing lists
>>>> to
>>>> pgFoundry and maintain their old addresses?
>>>
>>> All addresses would have to be changed to the pgfoundry.org one ...
>>
>> Ouch!  Moving my project off GBorg wasn't so hard, but forcing all mailing
>> list subscribers to move to a different address does hurt.
>>
>> If the same goes for many other projects on there, wouldn't it be possible
>> to move all mail handling for gborg.postgresql.org over to pgFoundry at
>> once, but preserve the domain name and list names?  It may help people
>> make the jump if mailing list migration could be decoupled from the other
>> changes.
>
> Actually, it should be entirely possible to setup forwarding for
> projects as they migrate, one-by-one. AFAIK mailman will handle
> something like project-blah@gbork.org being forwarded to
> project-blah@pgfoundry.org.

Woo hoo ... a mailman expert ... let us know how it is done so that we can 
do it :)

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664


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

Предыдущее
От: "Jim C. Nasby"
Дата:
Сообщение: Re: Memory profiling in postgreSQL
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: windows / initdb oddness