Re: Committers info for the git migration - URGENT!

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Committers info for the git migration - URGENT!
Дата
Msg-id AANLkTiktSrUOy-HH+dMvJi+kfuvW-BMa_CibQuo2fMD0@mail.gmail.com
обсуждение исходный текст
Ответ на Committers info for the git migration - URGENT!  (Magnus Hagander <magnus@hagander.net>)
Список pgsql-hackers
On Mon, Aug 16, 2010 at 9:38 AM, Magnus Hagander <magnus@hagander.net> wrote:
> Attention committers!!  ;)
>
> When we migrate to git, we will do a one-time mapping of your old
> username to an email address (as was discussed on the developer
> meeting in Ottawa earlier this year). This is stamped on every commit
> you have ever done, since that's how git works. It's part of the
> commit itself, so it *cannot* be changed once this is done. We can of
> course change which email address is used for *new* commits, but not
> for the existing once once they have gone in.
>
> The current mapping used is the same one as on git.postgresql.org (see
> attached file).
>
> Per discussions earlier on this list, we encourage people to use an
> email address that is permanent and stable, and does not for example
> change if you change your ISP or if you change employer. But in the
> end, the decision of which email address to use is up to you.
>
> If you want to *change* your email address from the one in the list
> attached here, please let me know *ASAP*. At the latest I need to know
> this before tuesday evening european time (see separate email about
> migration timeline).
>
> Since there is now a very tight timeline on this (sorry!), please ping
> any other committers you have on your IM/IRC list that you know don't
> read their -hackers email daily...

Please make me rhaas@postgresql.org - thanks.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


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

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: Git migration timeline
Следующее
От: Tom Lane
Дата:
Сообщение: Re: PL/pgSQL EXECUTE '..' USING with unknown