From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Git migration timeline |
Date: | 2010-08-16 15:53:06 |
Message-ID: | 1281973986.5303.7.camel@jd-desktop.unknown.charter.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2010-08-16 at 16:19 +0200, Magnus Hagander wrote:
> 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.
+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
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2010-08-16 15:59:44 | Re: "Bogus data in lock file" shouldn't be FATAL? |
Previous Message | Tom Lane | 2010-08-16 15:49:51 | Re: "Bogus data in lock file" shouldn't be FATAL? |