public inbox for [email protected]  

help / color / mirror / Atom feed

From: David Fetter <[email protected]>
To: Gregory Stark <[email protected]>
Cc: Zdenek Kotala <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: Posting to hackers and patches lists
Date: Sat, 10 May 2008 11:25:16 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Sat, May 10, 2008 at 10:55:57AM +0100, Gregory Stark wrote:
> "Zdenek Kotala" <[email protected]> writes:
> > Gregory Stark napsal(a):
> >> "Josh Berkus" <[email protected]> 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 <[email protected]> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: [email protected]

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

view thread (42+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Posting to hackers and patches lists
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox