Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1ebHFx-0002SJ-Cm
	for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Jan 2018 02:45:45 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1ebHFw-0003jN-3w
	for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Jan 2018 02:45:44 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1ebHFv-0003jC-Q0
	for pgsql-hackers@lists.postgresql.org; Tue, 16 Jan 2018 02:45:43 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1ebHFt-0004Cc-IN
	for pgsql-hackers@postgresql.org; Tue, 16 Jan 2018 02:45:42 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w0G2jY4u026719;
	Mon, 15 Jan 2018 21:45:34 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
cc: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>,
        Sergei Kornilov <sk@zsrv.org>,
        Michael Paquier <michael.paquier@gmail.com>,
        Andres Freund <andres@anarazel.de>,
        Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
        "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] Restricting maximum keep segments by repslots
In-reply-to: 
 <CA+TgmoZZNa6DUaoT0Bw3C420BBrshF5FY_L9Aa9CakC=hpCqqQ@mail.gmail.com>
References: <337571513944260@web55j.yandex.ru>
 <20180111.155910.26212237.horiguchi.kyotaro@lab.ntt.co.jp>
 <2798121515664527@web40g.yandex.ru>
 <20180115.150507.251293598.horiguchi.kyotaro@lab.ntt.co.jp>
 <CA+TgmoZZNa6DUaoT0Bw3C420BBrshF5FY_L9Aa9CakC=hpCqqQ@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Mon, 15 Jan 2018 21:34:05 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <26717.1516070734.1@sss.pgh.pa.us>
Date: Mon, 15 Jan 2018 21:45:34 -0500
Message-ID: <26718.1516070734@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Precedence: bulk

Robert Haas <robertmhaas@gmail.com> writes:
> Since the "Stripping trailing CRs from patch" message is totally
> harmless, I'm not sure why you should need to devote any effort to
> avoiding it.  Anyone who gets it should just ignore it.

Not sure, but that might be another situation in which "patch"
works and "git apply" doesn't.  (Feeling too lazy to test it...)

			regards, tom lane