On Mon, 2010-08-16 at 16:19 +0200, Magnus Hagander wrote:
> 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.
+1
JD
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt