Re: Git migration timeline

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Git migration timeline
Дата
Msg-id 3727.1281968104@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Git migration timeline  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: Git migration timeline  (Robert Haas <robertmhaas@gmail.com>)
Re: Git migration timeline  (Magnus Hagander <magnus@hagander.net>)
Список pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> On Mon, Aug 16, 2010 at 15:58, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I can see the point of wanting to be dead certain the repository isn't
>> changing under you during the data migration. �Perhaps we need an agreed
>> window between last call for commits and the actual lock-out.

> To prevent that, I just need to shut it down for 2 minutes to rsync
> the latest changes off it and onto the new git box. Maybe that's how
> we should do it.

That sounds like a reasonable scheme to me, especially since it leaves
the cvs repository functional.  Dunno about you, but I want a fallback
plan in case this turns into a disaster ...
        regards, tom lane


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

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: Git migration timeline
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Git migration timeline