Re: pgAccess change - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pgAccess change
Date
Msg-id 200003311444.JAA24711@candle.pha.pa.us
Whole thread Raw
In response to Re: pgAccess change  (Lamar Owen <lamar.owen@wgcr.org>)
List pgsql-hackers
> Bruce Momjian wrote:
> > > Thanks.  I'm building a test RPM here so I can satisfy Tom's request for
> > > regress results on CURRENT.  My rpm patchset barfed on pgaccess -- so I
> > > investigated.  I fixed it in my local tree, but wanted to alert folk.
>  
> > Glad you found it.  That was the one file I had to modify to get it to
> > match our old version, and obviously I messed that up.
> 
> I'm going to take this opportunity to thank Marc for having a cvsweb
> interface -- as I was able to see when the difference was introduced
> using that interface.
> 
> Given the number of things you patch, Bruce, it shouldn't surprise
> anyone that an occassional error is introduced -- that's why it's good
> to have many sets of eyes looking at the code.  I can only have
> nightmares about how many errors I could cause if I were applying
> patches at that rate... :-)

The problem with pgaccess is that is not a patch I can eyeball.  It is a
stand-alone tar file that writes over our files.  I am never sure what
is new or old until I see what files show as new, etc.

--  Bruce Momjian                        |  http://www.op.net/~candle pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: Docs refreshed
Next
From: Vince Vielhaber
Date:
Subject: Re: pgAccess change