Re: Git cvsserver serious issue - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Git cvsserver serious issue
Date
Msg-id 1285173899-sup-581@alvh.no-ip.org
Whole thread Raw
In response to Re: Git cvsserver serious issue  (Peter Eisentraut <peter_e@gmx.net>)
List 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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Thom Brown
Date:
Subject: Re: Configuring synchronous replication
Next
From: Abhijit Menon-Sen
Date:
Subject: Re: Git cvsserver serious issue