Re: [HACKERS] pgindent has been run

2006-10-05 Thread Michael Meskes
On Wed, Oct 04, 2006 at 04:41:44PM -0400, Bruce Momjian wrote: That will prevent it from being changed by pgindent in the future. Thanks. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber:

Re: [HACKERS] pgindent has been run

2006-10-04 Thread Michael Meskes
On Tue, Oct 03, 2006 at 08:26:36PM -0400, Bruce Momjian wrote: I have run pgindent for 8.2. Is there a way to make pgindent skip a directory? It seems it has changed all expected file in ecpg's regression suite. So we see a lot of differences now. Michael -- Michael Meskes Email: Michael at

Re: [HACKERS] pgindent has been run

2006-10-04 Thread Bruce Momjian
Michael Meskes wrote: On Tue, Oct 03, 2006 at 08:26:36PM -0400, Bruce Momjian wrote: I have run pgindent for 8.2. Is there a way to make pgindent skip a directory? It seems it has changed all expected file in ecpg's regression suite. So we see a lot of differences now. Sure a directory

Re: [HACKERS] pgindent has been run

2006-10-04 Thread Joachim Wieland
On Wed, Oct 04, 2006 at 06:15:31AM -0400, Bruce Momjian wrote: Michael Meskes wrote: Is there a way to make pgindent skip a directory? It seems it has changed all expected file in ecpg's regression suite. So we see a lot of differences now. Sure a directory can be skipped. I am confused

Re: [HACKERS] pgindent has been run

2006-10-04 Thread Bruce Momjian
Joachim Wieland wrote: On Wed, Oct 04, 2006 at 06:15:31AM -0400, Bruce Momjian wrote: Michael Meskes wrote: Is there a way to make pgindent skip a directory? It seems it has changed all expected file in ecpg's regression suite. So we see a lot of differences now. Sure a directory

[HACKERS] pgindent has been run

2006-10-03 Thread Bruce Momjian
I have run pgindent for 8.2. -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ?