DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	b=BjxDVwHt7v/z/k43FXY6pctPk+kuSVkpdkMsTlatYFS79dD//a7w1Ol//0jvkQv3wF
	PROx0E6R0VWKSFA+80iukxdl0EHUVhvZBBUmwuGgyTNCiKnxRVyZUnHpHQK0m2a9VuKF
	Ij8y2Xhv6n7u7Z4Ot1gY3IgGsXDuw6bpXbyr0=
Message-ID: <4CA169BB.8070805@gmail.com>
Date: Tue, 28 Sep 2010 13:06:19 +0900
From: Satoshi Nagayasu <satoshi.nagayasu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja;
	rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: Alvaro Herrera <alvherre@commandprompt.com>
CC: Greg Smith <greg@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>,
	Peter Eisentraut <peter_e@gmx.net>, pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: ECPG - Some errno definitions don't match to the manual
References: <4C4847D0.9030001@gmail.com>
	<AANLkTin286hRE0oLZFr4quDp6esNNztHmYUhfLO0vf_4@mail.gmail.com>
	<4C602E9D.40501@gmail.com> <4C60C7A9.10307@gmail.com>
	<AANLkTi=xFL3fbLxWJwAi7CJU9R_kiZSLF==3c9-vqRuG@mail.gmail.com>
	<4C634586.7090908@gmail.com>
	<1285502270.1601.1.camel@vanquo.pezone.net>
	<4CA11FF7.1090403@gmail.com>
	<AANLkTikF_=wz9aB4k4YmPD9jyfrAxspyCJwTWKkzCEyO@mail.gmail.com>
	<4CA13D11.7050905@gmail.com> <4CA1458F.9030707@2ndquadrant.com>
	<4CA15534.1060602@gmail.com> <1285645074-sup-514@alvh.no-ip.org>
In-Reply-To: <1285645074-sup-514@alvh.no-ip.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 2010/09/28 12:40, Alvaro Herrera wrote:
> Excerpts from Satoshi Nagayasu's message of lun sep 27 22:38:44 -0400 2010:
>> On 2010/09/28 10:31, Greg Smith wrote:
>>> If the patch you generated applies to the git version of the repo cleanly, you may be fine for now. The anon-cvs version is mainly intended as a source to get a copy of the source code just to compile or read, not to develop patches against. For that it would be better to switch to git when you get some time to spend on that.
>>
>> So, I have created another patch from git repository.
>> The attached one could be applied to the latest code.
>
> Looking at this patch I cannot but wonder if this should be a table
> instead of a plain list.

What's happen if you run the patch command at top of the repository?

[snaga@devwa02 postgresql]$ pwd
/home/snaga/pgsql/repo/postgresql
[snaga@devwa02 postgresql]$ patch -p1 < ../ecpg-git.sgml.diff
patching file doc/src/sgml/ecpg.sgml
[snaga@devwa02 postgresql]$

or

[snaga@devwa02 postgresql]$ git apply --reject ../ecpg-git.sgml.diff
../ecpg-git.sgml.diff:123: trailing whitespace.

Checking patch doc/src/sgml/ecpg.sgml...
Applied patch doc/src/sgml/ecpg.sgml cleanly.
warning: 1 line adds whitespace errors.
[snaga@devwa02 postgresql]$

Sorry I'm not familiar with Git yet, but I think above command can
apply the patch.
(I created the patch with the command `git diff'. Is this correct?)

Thanks,
-- 
NAGAYASU Satoshi <satoshi.nagayasu@gmail.com>