| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: New pg_lsn type doesn't have hash/btree opclasses |
| Date: | 2014-05-07 04:21:05 |
| Message-ID: | 5369B4B1.50306@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/07/2014 07:16 AM, Michael Paquier wrote:
> On Wed, May 7, 2014 at 8:07 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> On 2014-05-06 22:49:07 +0900, Michael Paquier wrote:
>> FWIW, the format you're using makes applying the patch including the
>> commit message relatively hard. Consider using git format-patch.
> Could you be clearer? By applying a filterdiff command or by using git
> diff? The latter has been used for this patch.
git format-patch -1
is usually what you want to emit a patch for the top commit. To produce
a patchset between the current branch and master:
git format-patch master
It doesn't use context diff, but I think people here have mostly stopped
caring about that now (?).
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2014-05-07 05:20:00 | Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers |
| Previous Message | Peter Geoghegan | 2014-05-07 03:56:54 | Re: Schizophrenic coding in gin_extract_jsonb(_hash) |