Re: How to submit a patch

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: How to submit a patch
Date: 2008-04-16 18:03:44
Message-ID: 20080416110344.12743b23@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

On Wed, 16 Apr 2008 13:59:50 -0400
Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:

>
> If you posted it last month then it was too late for the commit-fest
> that started on March 1, IIRC, so the fact that you didn't get
> feedback is hardly surprising - a commit-fest is like a
> mini-feature-freeze.

O.k. then what happens at that point? It wasn't in the queue for May (I
had to add it)

>
> As for the rest, we are still feeling our way a bit, as should have
> been apparent from the list emails, so formal documentation is
> probably premature.

I assumed the docs would be subject to change but "something" that
gives one off and not often patch submitters a clue is probably useful.
It also allows us to actually discuss a pattern of behavior we are
starting versus bouncing through 50 threads trying to figure out what's
next.

Sincerely,

Joshua D. Drake

--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgresql.us/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2008-04-16 18:04:17 Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout
Previous Message Andrew Dunstan 2008-04-16 17:59:50 Re: How to submit a patch

Browse pgsql-www by date

  From Date Subject
Next Message Bruce Momjian 2008-04-16 18:10:30 Re: How to submit a patch
Previous Message Andrew Dunstan 2008-04-16 17:59:50 Re: How to submit a patch