| 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: | Alfred Perlstein <bright(at)wintelcom(dot)net>, The Hermit Hacker <scrappy(at)hub(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgindent run? |
| Date: | 2001-03-22 15:36:24 |
| Message-ID: | 29324.985275384@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:
>> Alfred Perlstein <bright(at)wintelcom(dot)net> writes:
> cvs annotate is a really, really handy tool, unfortunetly these
> indent runs remove this very useful tool as well as do a major job
> of obfuscating the code changes.
>>
>> I think this is a good reason for *not* applying pgindent on an
>> incremental basis, but only once per release cycle. That at least
>> lets cvs annotate be useful within a cycle.
> What about having it happen on every CVS commit?
Try that and you'll get all-out war. It's tough enough keeping in sync
with the repository already.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-03-22 15:37:14 | Re: pgindent run? |
| Previous Message | The Hermit Hacker | 2001-03-22 15:33:33 | solaris 7/sparc good to go: |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-03-22 15:37:14 | Re: pgindent run? |
| Previous Message | Bruce Momjian | 2001-03-22 15:09:38 | Re: pgindent run? |