Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 1953F2E002D for ; Wed, 7 May 2008 11:25:31 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 19171-01 for ; Wed, 7 May 2008 11:25:10 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.187]) by developer.postgresql.org (Postfix) with ESMTP id CC6CE2E0060 for ; Wed, 7 May 2008 11:25:18 -0300 (ADT) Received: by ti-out-0910.google.com with SMTP id y8so110695tia.5 for ; Wed, 07 May 2008 07:25:16 -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=63KWPypXhStgNFW0mWWqE6DQ0H6zZhoxjphpAnXVbU0=; b=IdwftBP1eEot6f6mIwNyNfBj9WxOsJDH/xQddVuucKX+Eg83VswIrb2Ju3ruTUuGqt/OicaLD1jJAkE9TKor7XjTNJPDlPCKxzUzDbP1HyeUIlC+AJVmW411zDQ7hsvBztNid1W5gpY6IgSrsoD0D0FBv8jziUhwStvcs0EbxfY= 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=Kd7/tUupp/8UlVWF8P+bjoIqC/itcV1sRZC8rDozGk+zaLt3ZEH6O1cj2IuRRMC9XNGVMpHMWf8YU5d1lhosKyP5F4r1hOiVpSe+wOKRLbHe+haoQf7HrZmAGLwQ0NKkjjCltj3qn8/ItSBgK3RG3BveBKJB5jlPRlvooj8wE4I= Received: by 10.110.70.5 with SMTP id s5mr203184tia.21.1210170316072; Wed, 07 May 2008 07:25:16 -0700 (PDT) Received: by 10.110.21.8 with HTTP; Wed, 7 May 2008 07:25:16 -0700 (PDT) Message-ID: <37ed240d0805070725oa5778b1q9ed77349fdcc24f4@mail.gmail.com> Date: Thu, 8 May 2008 00:25:16 +1000 From: "Brendan Jurd" To: "Tom Lane" Subject: Re: Posting to hackers and patches lists Cc: "Bruce Momjian" , PostgreSQL-development In-Reply-To: <6229.1210169873@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200805071408.m47E8Qt22784@momjian.us> <6229.1210169873@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/164 X-Sequence-Number: 118163 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. > * reviewer won't know if the submitter changes the patch after he > downloads a copy, and in fact nobody will ever know unless the submitter > takes the time to compare the eventual commit to what he thinks the > patch is > Well, as long as you send another message to the lists saying "I've uploaded a new version of the patch, that URL again is <>". If you just silently update the patch without telling anybody you're bound to run into problems. Cheers, BJ