Skip site navigation (1) Skip section navigation (2)

pgbuildfarm - client-code: Sanity check for cvs merge conflicts.

From: andrewd(at)pgfoundry(dot)org (User Andrewd)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgbuildfarm - client-code: Sanity check for cvs merge conflicts.
Date: 2005-08-02 00:22:53
Message-ID: 20050802002253.C4AED112620C@pgfoundry.org (view raw or flat)
Thread:
Lists: 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

Next:From: Tom LaneDate: 2005-08-02 01:35:23
Subject: pgsql: Back-port several small portability fixes to get contrib building
Previous:From: User AndrewdDate: 2005-08-02 00:10:11
Subject: pgbuildfarm - client-code: Cygwin sanity check for running cygserver.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group