| From: | Brook Milligan <brook(at)biology(dot)nmsu(dot)edu> |
|---|---|
| To: | maillist(at)candle(dot)pha(dot)pa(dot)us |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] pgaccess seems a tad confused |
| Date: | 1999-09-17 15:48:03 |
| Message-ID: | 199909171548.JAA22349@biology.nmsu.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 1. Why did the new pgaccess get installed into REL6_5 branch but not
> main development branch?
>
No sense putting in development because there will probably be a newer
version by the time 6.6 is released, no?
Yes there will be, but it seems to serve two purposes. One is that
anyone working with the development tree at least has some version of
pgaccess handy. More importantly, though, any bugs in the Makefile or
whatever will be noticed early by developers and won't wait until the
last moment. Since the basic installation scheme likely doesn't
depend much on the exact pgaccess release, there really isn't much to
be lost by keeping it in the development tree.
Cheers,
Brook
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-09-17 16:44:17 | Re: [HACKERS] pgaccess seems a tad confused |
| Previous Message | Bruce Momjian | 1999-09-17 15:47:59 | Re: [HACKERS] Re: attdisbursiont |