Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 1AD781337B81 for ; Thu, 30 Sep 2010 20:58:55 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 77344-04 for ; Thu, 30 Sep 2010 23:58:48 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mail.postgresql.org (Postfix) with ESMTP id 2A1C21337B85 for ; Thu, 30 Sep 2010 20:58:48 -0300 (ADT) Received: from [192.168.1.6] (static-71-179-240-8.bltmmd.fios.verizon.net [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0LbNoU-1OMKlb32eA-00kLdb; Fri, 01 Oct 2010 01:58:38 +0200 Message-ID: <4CA5242C.3090707@2ndquadrant.com> Date: Thu, 30 Sep 2010 19:58:36 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Satoshi Nagayasu CC: Magnus Hagander , Peter Eisentraut , Tom Lane , Robert Haas , pgsql-docs Subject: Re: ECPG - Some errno definitions don't match to the manual References: <4C4847D0.9030001@gmail.com> <4C602E9D.40501@gmail.com> <4C60C7A9.10307@gmail.com> <4C634586.7090908@gmail.com> <1285502270.1601.1.camel@vanquo.pezone.net> <4CA11FF7.1090403@gmail.com> <4CA13D11.7050905@gmail.com> <4CA1458F.9030707@2ndquadrant.com> <17708.1285656381@sss.pgh.pa.us> <1285676832.20420.2.camel@vanquo.pezone.net> <4CA43586.7050503@2ndquadrant.com> <4CA4B97B.7010509@gmail.com> In-Reply-To: <4CA4B97B.7010509@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:yyJI10XMbCXAO5amP1bR6VEu2+bDIFDY1y57mqtlHgE iH8Gh/gAJN5BA3LUAYUiySNDxF1cXY3/ntZGSShAV4oAAwBDKX TLW6eBMHu+nWR7Khs5Y1arH+SjO6vENY5cg5uwUI1qhhctTH6Q bdvb2+VoQgm3/ASsby70TS1sGZXo8Xec8tEAr17WaNa5ijUoND uKSr7vFxJIx6Z7kS4u1RiNaXtI2y8Ukj6bIY+XaTbg= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201009/151 X-Sequence-Number: 6141 Satoshi Nagayasu wrote: > I think the easiest way to avoid(my) misunderstanding is > to put some note, like "Use Git to make your patch", > on the Coding page. > > http://www.postgresql.org/developer/coding If you visit that page again right now, you'll find it hard to reach a destination that doesn't talk about git instead of CVS. "Information about the Source Code Repository", the FAQ, "Developer Section on wiki.postgresql.org", every one of those has now been corrected. The one way left you can still get the impression the project uses CVS will go away when 9.0.1 ships, but even that one is a secondary link--one you only see after a visit to a page talking about git. Thanks for the report and sorry about the confusion. I don't think people who visit the "Coding" page are likely to run into the problem you did at this point anymore. Everything that can be easily cleaned up is now, and that one stray CVS reference will go away shortly. -- Greg Smith, 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services and Support www.2ndQuadrant.us Author, "PostgreSQL 9.0 High Performance" Pre-ordering at: https://www.packtpub.com/postgresql-9-0-high-performance/book