From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Git migration timeline |
Date: | 2010-08-16 14:18:24 |
Message-ID: | AANLkTi=mvwSSp-BABGg9aOKAojGppCWQuhPxFwP7gdeP@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 16, 2010 at 10:15 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> On Mon, Aug 16, 2010 at 15:58, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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 ...
I don't think anybody proposed permanently deleting the CVS repository.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2010-08-16 14:19:10 | Re: Git migration timeline |
Previous Message | Robert Haas | 2010-08-16 14:17:27 | Re: Committers info for the git migration - URGENT! |