Re: PostgreSQL Developer meeting minutes up - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: PostgreSQL Developer meeting minutes up
Date
Msg-id 20090529154209.GB10092@alvh.no-ip.org
Whole thread Raw
In response to Re: PostgreSQL Developer meeting minutes up  (Aidan Van Dyk <aidan@highrise.ca>)
Responses Re: PostgreSQL Developer meeting minutes up  (Aidan Van Dyk <aidan@highrise.ca>)
List pgsql-hackers
Aidan Van Dyk wrote:

> Yes, but the point is you want an exact replica of CVS right?  You're
> git repo should have $PostgreSQL$ and the cvs export/checkout (you do
> use -kk right) should also have $PostgreSQL$.
> 
> The 3 parsecvs errors were that it *didn't* recognoze the strange
> $PostgreSQL ... Exp $ expansion that cvs did.

Huh, no -- I agree that $OpenBSD$ etc should remain (we don't munge them
anyway), but $PostgreSQL$, $Id$, $Revision$ etc tags are best gone
because, as Markus says, their expansion interferes with content hashing.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Python 3.0 does not work with PL/Python
Next
From: "David E. Wheeler"
Date:
Subject: Re: plperl error format vs plpgsql error format vs pgTAP