From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Kris Jurka <books(at)ejurka(dot)com>, pgsql-hackers(at)postgresql(dot)org, Michael Meskes <meskes(at)postgresql(dot)org> |
Subject: | Re: CVS corruption/mistagging? |
Date: | 2007-08-15 00:01:23 |
Message-ID: | 17635.1187136083@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Looking at the Committers mail, it looks like there have only been two
> very small commits since Michael's series of commits around 12 to 13.5
> hours ago, and before that nothing since around 28 hours ago. Do we have
> a backup snapshot of the repo taken during that time that we can roll
> back to? That might be simpler than doing surgery on the repo.
It looks to me like the mistake was unrelated to any commit, and was
made at Aug 12 09:50 UTC. (Aside from the file-timestamp evidence,
caracara's build failure at 2007-08-12 213845 shows that the problem
is more than 2 days old.) I count seven commits of my own and several
of Michael's since then. If I'm right that a simple "cvs rtag" will fix
it, I'd rather do that than try to reapply patches.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-08-15 00:33:49 | Re: CVS corruption/mistagging? |
Previous Message | Jeff Davis | 2007-08-14 23:58:27 | Re: Index Tuple Compression Approach? |