From: Andrew Dunstan <andrew@dunslane.net>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: pgindent run coming
Date: Thu, 11 Jun 2009 13:10:30 -0400
Message-ID: <4A313A86.20808@dunslane.net> (raw)
In-Reply-To: <20090611151814.GA6401@alvh.no-ip.org>
References: <200906111450.n5BEoD817208@momjian.us>
<13910.1244732413@sss.pgh.pa.us>
<4A311E59.5080202@dunslane.net>
<20090611151814.GA6401@alvh.no-ip.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: andrew@dunslane.net, alvherre@commandprompt.com, tgl@sss.pgh.pa.us, bruce@momjian.us
Subject: Re: pgindent run coming
In-Reply-To: <4A313A86.20808@dunslane.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox