Re: New pg_lsn type doesn't have hash/btree opclasses

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: New pg_lsn type doesn't have hash/btree opclasses
Дата
Msg-id CAB7nPqStrxb3xxBRHzURnTJMu2bBiWuwpqg06hWHxNXv-+kM=g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: New pg_lsn type doesn't have hash/btree opclasses  (Craig Ringer <craig@2ndquadrant.com>)
Список pgsql-hackers
On Wed, May 7, 2014 at 1:21 PM, Craig Ringer <craig@2ndquadrant.com> wrote:
> 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 (?).
Thanks for the details, I didn't know this subcommand of git.
-- 
Michael



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: [v9.5] Custom Plan API
Следующее
От: Kouhei Kaigai
Дата:
Сообщение: Re: [v9.5] Custom Plan API