Re: New idea for patch tracking

From: "Dave Page" <dpage(at)postgresql(dot)org>
To: "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: New idea for patch tracking
Date: 2007-05-05 07:35:27
Message-ID: 200705050835280000@2134815378
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> ------- Original Message -------
> From: Bruce Momjian <bruce(at)momjian(dot)us>
> To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
> Sent: 05/05/07, 03:00:25
> Subject: [HACKERS] New idea for patch tracking
>
> As for #3, again, I don't want us to take on a burdensome patch tracking
> process that is more effort than it is worth, and the lack of people
> jumping to even manage a simple web page for current 8.3 patches has me
> questioning what kind of support a burdensome tracking system would
> receive.

I don't recall hearing you ask for people to help with a web page.

> What I think we can do simply is to have our email software automatically
> number emails submitted to the patches list that already don't have a
> number. This way, all followups, even if moved to the hackers list, would
> maintain that patch number, and if an updated version is posted, the user
> would keep the same number in the email subject.

<snip tracker outline>

Barring a few trivial details, that sounds almost identical to what I proposed.

Regards, Dave

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2007-05-05 08:34:00 Re: how does one set the plpython python interpreter?
Previous Message Neil Conway 2007-05-05 07:22:31 Integer datetimes