Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 1BFDF2E005F for ; Sat, 10 May 2008 15:25:25 -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 06618-03 for ; Sat, 10 May 2008 15:25:19 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from fetter.org (start.fetter.org [66.92.188.65]) by developer.postgresql.org (Postfix) with ESMTP id 86FD32E0031 for ; Sat, 10 May 2008 15:25:21 -0300 (ADT) Received: by fetter.org (Postfix, from userid 500) id EF566FBC9F2; Sat, 10 May 2008 11:25:16 -0700 (PDT) Date: Sat, 10 May 2008 11:25:16 -0700 From: David Fetter To: Gregory Stark Cc: Zdenek Kotala , Josh Berkus , pgsql-hackers@postgresql.org Subject: Re: Posting to hackers and patches lists Message-ID: <20080510182516.GC18958@fetter.org> References: <34d269d40805070752g4d578a1fu6acb00fd8e5f774e@mail.gmail.com> <34d269d40805070837q19f1144eu8c316fa1cf6d8780@mail.gmail.com> <4821D0A0.8040305@zeut.net> <200805081043.54942.josh@agliodbs.com> <87zlr0mqn9.fsf@oxford.xeocode.com> <482559F8.7020206@sun.com> <87abiy7aaa.fsf@oxford.xeocode.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87abiy7aaa.fsf@oxford.xeocode.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/303 X-Sequence-Number: 118302 On Sat, May 10, 2008 at 10:55:57AM +0100, Gregory Stark wrote: > "Zdenek Kotala" writes: > > Gregory Stark napsal(a): > >> "Josh Berkus" writes: > >> > >>> How about hacking together a simple patch tracker instead, as > >>> Bruce suggested? I've never found e-mail to be a particularly > >>> good way to track patches. > >> > >> The thing is that we don't just want to "track" patches. We want > >> to talk about patches. > > > > I think we want to have both. If you have big patch you don't want > > go through all patch again and again when new version is released > > with only few changes. If you are able to have diff between two > > patch versions you are able preform easy check if all comments are > > already fixed. > > Ah, that's not something a patch tracker or a mailing list would > solve. There is a tool that would solve this -- a revision control > system. There's already an official git repository, and it plays nicely with the official CVS it sits on top of :) http://git.postgresql.org/ Cheers, David. -- David Fetter http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate