| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: git: uh-oh |
| Date: | 2010-08-17 19:28:46 |
| Message-ID: | AANLkTingtmzi43CeQrXS1OHmbWMRwobcD1gYRXjyEpbB@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 17, 2010 at 3:23 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> The tip of every branch, and every single tag, all have the correct
> data in them, but some revisions in between seem majorly confused.
It seems to me that what we'll need to do here is write a script to
look through the CVS history of each file and make sure that the
versions of that file which appear on each branch match the revs in
CVS in content, order, and the commit message associated with any
changes. However, that's not going to do get done today.
>>> It's too bad that nobody noticed this sooner, but I'm glad I noticed
>>> today rather than tomorrow.
>>
>> We're not going to start using the git repository until everyone is
>> satisfied it's OK, both as to current contents and history.
Duh. But obviously no one's checked that carefully enough up until now.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-17 19:29:48 | Re: git: uh-oh |
| Previous Message | Christopher Browne | 2010-08-17 19:26:33 | Re: Additional git conversion steps |