| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgindent run? |
| Date: | 2001-03-22 04:35:07 |
| Message-ID: | 8041.985235707@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Hey, I am open to whatever people want to do. Just remember that we
> accumulate lots of patches/development during the slow time before
> development, and those patches become harder to apply. Peter E has some
> already.
Why not start a devel cycle by (a) branching the tree, (b) applying
all held-over patches, and then (c) running pgindent?
I'd probably wait a week or so between (a) and (c) to let people push
in whatever they have pending. But in general it seems a lot safer
to pgindent at the front end of the cycle not the back end.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-03-22 04:36:50 | Re: Re: RELEASE STOPPER? nonportable int64 constants in pg_crc.c |
| Previous Message | Tom Lane | 2001-03-22 04:24:57 | Re: More on elog and error codes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-03-22 04:45:17 | Re: pgindent run? |
| Previous Message | The Hermit Hacker | 2001-03-22 04:16:13 | Re: pgindent run? |