Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 207F42E004B for ; Wed, 7 May 2008 11:52:41 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 62849-05 for ; Wed, 7 May 2008 11:52:27 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.187]) by developer.postgresql.org (Postfix) with ESMTP id 1AA362E0052 for ; Wed, 7 May 2008 11:52:32 -0300 (ADT) Received: by fk-out-0910.google.com with SMTP id e30so506723fke.3 for ; Wed, 07 May 2008 07:52:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=voBNhjyZi84S6A3iCso+PQAd3dmSaEOrewkB1fs8K6Y=; b=rfAFMWtVNoHRRVdI7FlLABGLWYv3JmKG/dc5Z6uewKUvHqRPEwa2ma8YExwR5vOigFpQso9MqKAfXZnte+8rlUlsy7oR76Nltj/gXdFwrs0C5P+LXBOBlDiQJ6k4KSa8Z4QiQKnmVW2XxZYcfDmnWCmRyn8ivrL2DQU2PQI1/pU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OtIt2OaaTC4r6HWvqRRL7t7K3TOQUxYxUOGPfFfKfmkXUAvbguyimXQwvglg1elTEUxs3FX1tOndERYIXT2SqfGtGuXJyRXBrWRV3/uQ0hBGPi7njhDFcYg2OIKZlxeDdWBS5z0XqWOE9Za80w3EBh9jeQ+EO1iY+K0feM4j8d0= Received: by 10.82.187.2 with SMTP id k2mr212276buf.55.1210171951327; Wed, 07 May 2008 07:52:31 -0700 (PDT) Received: by 10.82.177.10 with HTTP; Wed, 7 May 2008 07:52:31 -0700 (PDT) Message-ID: <34d269d40805070752g4d578a1fu6acb00fd8e5f774e@mail.gmail.com> Date: Wed, 7 May 2008 08:52:31 -0600 From: "Alex Hunsaker" To: "Bruce Momjian" Subject: Re: Posting to hackers and patches lists Cc: "Brendan Jurd" , "Tom Lane" , PostgreSQL-development In-Reply-To: <200805071428.m47ESdI04278@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <37ed240d0805070725oa5778b1q9ed77349fdcc24f4@mail.gmail.com> <200805071428.m47ESdI04278@momjian.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/170 X-Sequence-Number: 118169 On Wed, May 7, 2008 at 8:28 AM, Bruce Momjian wrote: > Brendan Jurd wrote: > > On Thu, May 8, 2008 at 12:17 AM, Tom Lane wrote: > > > Bruce Momjian writes: > > > > I think it would be helpful for us to provide an infrastructure where > > > > people who don't run their own servers to store their patches at a > > > > stable URL where they can keep updating the content. I did that with > > > > the psql wrap patch and it helped me. > > > > > > Actually, I find that that is a truly awful habit and I wish that people > > > would *not* do it that way. There are two reasons why not: > > > > > > * no permanent archive of the submitted patch > > > > > > > Yes. I can see how posting a URL to a patch would be convenient, but > > having the permanent record of the patch as submitted is important. > > > > What about uploading patches to the wiki? That way we have the > > permanent record (change history), as well as the single authoritative > > location for fetching the latest version. > > Right, I was assuming once the patch was uploaded it would be to our > infrastructure and would be permanent. Heck, I dont think patch submitters really care. And Ill do whatever is in the dev faq. But Its a heck of a lot easier (for me) just to send them in email. Plus it seems awkward to move a discussion thats taking place on -hackers over to patches... Granted I could post to patches first, wait an hour then send an email to hackers/reviewer and say hey! updated patch here! But it hardly seems worth it to me... In fact I would argue -patches should go away so we dont have that split.