Re: pgindent run?

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:48:09
Message-ID: Pine.BSF.4.33.0103220047050.48022-100000@mobile.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Wed, 21 Mar 2001, Bruce Momjian wrote:

> > 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?
>
> If people can get their patches in all at one time, that would work.
> The only problem there is that people who supply patches against 7.1
> will not match the 7.2 tree, and we get those patches from people for
> months.

and those patches should only be applied to the v7.1 branch ... we are
suggesting (or, at least, I am) is that you pgindent *HEAD* after we've
branched off v7.1 ...

... that way, we go into the new dev cycle "clean", but we doon't mess up
the *STABLE* tree ...

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-03-22 04:50:46 Re: pgindent run?
Previous Message Philip Warner 2001-03-22 04:47:52 Re: More on elog and error codes

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2001-03-22 04:50:46 Re: pgindent run?
Previous Message Bruce Momjian 2001-03-22 04:45:17 Re: pgindent run?