From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter T Mount <peter(at)retep(dot)org(dot)uk> |
Cc: | PostgreSQL Hackers List <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] CVS and the backend |
Date: | 1998-08-06 01:37:35 |
Message-ID: | 6143.902367455@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter T Mount <peter(at)retep(dot)org(dot)uk> writes:
> I've just run CVS UPDATE again, in another attempt to get initdb to run.
> Anyhow, I noticed that there was a message saying that there were
> conflicts. Any ideas?
That means CVS got confused about how to update your local file.
Typically, it means that the file now on your disk is broken ---
it will have both versions of the conflicting text. CVS is expecting
you to sort it out, which would be the right thing if the difference
involved a change that you needed to commit to the source tree.
If the conflict is in a file that you have not got interesting private
changes in, the best thing is just to delete the local copy of that file
and do cvs update again to fetch a clean copy.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-08-06 02:04:48 | Re: [HACKERS] SPI procedure for removing large objects |
Previous Message | David Hartwig | 1998-08-05 22:08:32 | WHERE xmin = 9999 |