Message-ID: <4A313A86.20808@dunslane.net>
Date: Thu, 11 Jun 2009 13:10:30 -0400
From: Andrew Dunstan <andrew@dunslane.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text
	SeaMonkey/1.0.9
MIME-Version: 1.0
To: Alvaro Herrera <alvherre@commandprompt.com>
CC: Tom Lane <tgl@sss.pgh.pa.us>, Bruce Momjian <bruce@momjian.us>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: pgindent run coming
References: <200906111450.n5BEoD817208@momjian.us>
	<13910.1244732413@sss.pgh.pa.us> <4A311E59.5080202@dunslane.net>
	<20090611151814.GA6401@alvh.no-ip.org>
In-Reply-To: <20090611151814.GA6401@alvh.no-ip.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Alvaro Herrera wrote:
> BTW if we had an "official" typedef list that could be used for the
> length of a whole major release, we could run pgindent on a regular
> basis (say fortnightly or monthly); patch submitters would just need to
> run it on their own trees to avoid merge conflicts.
>
> (Hmm, but I'm unsure how would that work with git merge etc).
>
>   

Well, step one was finding a way to get a more comprehensive typedef 
list. Now we have some sort of mechanism for doing that, we can look at 
regularly pulling the list into the source, I guess. Maybe then we could 
look at either regular runs or even making it a part of a commit to the 
central repo, if we trust it enough. That would have the advantage of 
avoiding any later merge problems.

After the release, we can play around some more.

cheers

andrew