| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Ali Akbar <the(dot)apaan(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [REVIEW] Re: Fix xpath() to return namespace definitions |
| Date: | 2015-01-19 00:00:34 |
| Message-ID: | CAB7nPqR681+rMy_kLqqQgiBufb0g=n9E6p-vA_q6yK_TniF1Xw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 19, 2015 at 2:38 AM, David Fetter <david(at)fetter(dot)org> wrote:
> On Sun, Jan 18, 2015 at 06:05:05PM +0700, Ali Akbar wrote:
>> 2015-01-18 10:44 GMT+07:00 Peter Eisentraut <peter_e(at)gmx(dot)net>:
>> Btw, for bug-fix patches like this, should the patch creator (me) also
>> create patches for back branches?
>
> As I understand it, back-patches are the committer's responsibility.
> The submitter might make suggestions as to how this might be
> approached if it doesn't appear trivial.
TBH, I would imagine that patches that can be applied to back-branches
are a better start point than plain scratch particularly if there are
diffs in stable branches compared to HEAD. Everybody's time is
important.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-01-19 00:02:54 | Re: Re: Better way of dealing with pgstat wait timeout during buildfarm runs? |
| Previous Message | Noah Misch | 2015-01-18 23:48:41 | Re: Re: Better way of dealing with pgstat wait timeout during buildfarm runs? |