Gregory Stark napsal(a):
> "Zdenek Kotala" <Zdenek.Kotala@Sun.COM> writes:
>
>> Gregory Stark napsal(a):
>>> "Josh Berkus" <josh@agliodbs.com> 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.

OK. I little bit confused what patch tracer should do. Is it only for tracking
discuss about patches?

> We aren't using CVS the way it's really intended. If all this development
> happened on branches then people could go look at the current version at any
> point, not just when authors decide to announce it. And people could generate
> diffs between the last time they looked at that branch and now etc.

Yeah, I discussed this with Peter E. during his Prague visit and it should be
big deal for code reviewing and new feature development.

Zdenek


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On Sat, May 10, 2008 at 10:55:57AM +0100, Gregory Stark wrote:
> "Zdenek Kotala" <Zdenek.Kotala@Sun.COM> writes:
> > Gregory Stark napsal(a):
> >> "Josh Berkus" <josh@agliodbs.com> 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 <david@fetter.org> 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

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

At 2008-06-26 18:51:46 -0400, bruce@momjian.us wrote:
>
> I propose we close the patches list and tell everyone to start using
> only the hackers list.

That's an excellent idea.

-- ams

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On 5/7/08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Matthew T. O'connor" <matthew@zeut.net> writes:
> > By the way, what is the actual size limit on hackers vs patches.
>
> They do have different size limits; we'd have to raise the limit on
> -hackers if we do this. Marc would know exactly what the limits are.

Seems it's below 30k as my 34k (gz) patch was dropped yesterday.

--
marko

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Try now, just raised it to the same as -patches (100k) ...


- --On Saturday, June 28, 2008 12:59:18 +0300 Marko Kreen <markokr@gmail.com>
wrote:

> On 5/7/08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> "Matthew T. O'connor" <matthew@zeut.net> writes:
>> > By the way, what is the actual size limit on hackers vs patches.
>>
>> They do have different size limits; we'd have to raise the limit on
>> -hackers if we do this. Marc would know exactly what the limits are.
>
> Seems it's below 30k as my 34k (gz) patch was dropped yesterday.
>
> --
> marko
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers



- --
Marc G. Fournier Hub.Org Hosting Solutions S.A. (http://www.hub.org)
Email . scrappy@hub.org MSN . scrappy@hub.org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkhmMjkACgkQ4QvfyHIvDvPuNgCgj0qvwSIkI3 nuqa1tHpcaNzd5
n4gAoJXJFJUiTPN5qWQ/hUBiaCBXniCK
=blIw
-----END PGP SIGNATURE-----


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers