Re: New pg_lsn type doesn't have hash/btree opclasses - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: New pg_lsn type doesn't have hash/btree opclasses
Date
Msg-id 5369B4B1.50306@2ndquadrant.com
Whole thread Raw
In response to Re: New pg_lsn type doesn't have hash/btree opclasses  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: New pg_lsn type doesn't have hash/btree opclasses
List pgsql-hackers
On 05/07/2014 07:16 AM, Michael Paquier wrote:
> On Wed, May 7, 2014 at 8:07 AM, Andres Freund <andres@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Schizophrenic coding in gin_extract_jsonb(_hash)
Next
From: Simon Riggs
Date:
Subject: Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers