pgbuildfarm - client-code: Sanity check for cvs merge conflicts. - Mailing list pgsql-committers

From andrewd@pgfoundry.org (User Andrewd)
Subject pgbuildfarm - client-code: Sanity check for cvs merge conflicts.
Date
Msg-id 20050802002253.C4AED112620C@pgfoundry.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Sanity check for cvs merge conflicts. This should not normally happen
but if people monkey with the source dir (e.g. by doing configure or build
in it, and expecially if they test their changes there instead of in a copy,
this can happen. CVS at least on some systems doesn't exit with failure
in such cases, so we look for the status lines that give it away.

Modified Files:
--------------
    client-code:
        run_build.pl (r1.43 -> r1.44)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbuildfarm/client-code/run_build.pl.diff?r1=1.43&r2=1.44)

pgsql-committers by date:

Previous
From: andrewd@pgfoundry.org (User Andrewd)
Date:
Subject: pgbuildfarm - client-code: Cygwin sanity check for running cygserver.
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Back-port several small portability fixes to get contrib building