Re: Git migration timeline - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Git migration timeline
Date
Msg-id AANLkTimAPGPPmJ=0vgoLodGST=UNp3au_LzKpSEiG5tF@mail.gmail.com
Whole thread Raw
In response to Re: Git migration timeline  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Git migration timeline  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Git migration timeline  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
On Mon, Aug 16, 2010 at 16:15, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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 ...

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/


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Git migration timeline
Next
From: Robert Haas
Date:
Subject: Re: Committers info for the git migration - URGENT!