Re: async notification patch for dblink

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>, "Marcus Kempe" <marcus(at)kempe(dot)cc>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: async notification patch for dblink
Date: 2009-08-04 02:18:51
Message-ID: 27370.1249352331@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joe Conway <mail(at)joeconway(dot)com> writes:
> BTW, some commitfest procedural comments/questions:

> 1) I couldn't figure out how to attach my patch to the commitfest page
> short of cut-n-paste into the small comment text box -- is that my only
> choice?

No, what you should do is first send the patch to -hackers, then put the
message-ID of that email into the place provided. The comment box isn't
really meant for much more than a one-line summary of the message being
linked to.

> 3) I couldn't see any way to assign myself as the committer.

Yeah, the webapp doesn't explicitly record the committer for a patch.
What I've been doing is adding a comment saying that I'm taking a patch
to commit. A separate field would probably be better though.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2009-08-04 02:19:48 Re: SE-PostgreSQL Specifications
Previous Message Brendan Jurd 2009-08-04 02:09:50 Re: WIP: to_char, support for EEEE format