Re: Git cvsserver serious issue

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Git cvsserver serious issue
Date: 2010-09-22 16:45:52
Message-ID: 1285173899-sup-581@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members pgsql-hackers

Excerpts from Peter Eisentraut's message of mié sep 22 12:21:45 -0400 2010:

> Well, let's see. If someone can figure out the git equivalent of
>
> if cvs -q update | egrep -q '^(U|P) '; then
> # ... something changed, so run the update ...
> fi
>
> (assuming, for simplicity, that the current directory has the
> appropriate branch checked out already)
>
> then I might be able to get this fixed.

Would it work to save the previous commit hash in a file and compare to
the current one?

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse buildfarm-members by date

  From Date Subject
Next Message Abhijit Menon-Sen 2010-09-22 16:47:13 Re: Git cvsserver serious issue
Previous Message Robert Haas 2010-09-22 16:42:17 Re: Git cvsserver serious issue

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-09-22 16:46:52 Re: Configuring synchronous replication
Previous Message Thom Brown 2010-09-22 16:43:00 Re: Configuring synchronous replication