Re: Git migration timeline

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Git migration timeline
Date: 2010-08-16 14:19:10
Message-ID: AANLkTimAPGPPmJ=0vgoLodGST=UNp3au_LzKpSEiG5tF@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 16, 2010 at 16:15, 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 ...

Oh, I had no intention whatsoever of *removing* it. Just disabling login to it.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-08-16 14:33:12 Re: PL/pgSQL EXECUTE '..' USING with unknown
Previous Message Robert Haas 2010-08-16 14:18:24 Re: Git migration timeline