From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Git migration timeline |
Date: | 2010-08-16 14:15:04 |
Message-ID: | 3727.1281968104@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-08-16 14:15:21 | Re: Git migration timeline |
Previous Message | Magnus Hagander | 2010-08-16 14:08:50 | Re: Git migration timeline |