Re: How can I check the treatment of bug fixes?

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, MauMau <maumau307(at)gmail(dot)com>
Subject: Re: How can I check the treatment of bug fixes?
Date: 2011-05-27 21:54:35
Message-ID: 201105272354.36678.andres@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Friday, May 27, 2011 20:39:26 Robert Haas wrote:
> On Fri, May 27, 2011 at 2:19 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> >> On Fri, May 27, 2011 at 12:21 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >>> That patch is waiting for a committer who knows something about Windows
> >>> to pick it up.
> >>
> >> It might be useful, in this situation, for the OP to add this patch to
> >> the CommitFest application.
> >>
> >> https://commitfest.postgresql.org/action/commitfest_view/open
> >>
> >> Also, I think it's about time we got ourselves some kind of bug
> >> tracker.
> >
> > [ shrug... ] I think the main problem is a lack of committer cycles.
> > If so, the extra bureaucracy involved in managing a bug tracker will
> > make things worse, not better.
> >
> > However, if someone *else* wants to do the work of entering bugs into a
> > tracker and updating their status, far be it from me to stand in their
> > way.
> And who is to say only committers can fix bugs? Actually commit the
> fixes themselves, yes. Write the patches? No.
If I see a bug in a region I know something about and its on a platform I care
about (i.e. likely only linux) I try to do this. But its hard, in most
situations one of you already did it. Tom and you are just to goddamn fast in
many, many cases. Which is totally great, don't get me wrong, but makes it
hard to beat you as a mere mortal ;)

Do you like separate patches for the back branches or is that basically
useless work?

Related to doing stuff like that is that I really find it hard to write a patch
that happens to be liked by Tom or you so it does not have to be mostly
rewritten. For that to change for one I would like to have the Coding Style to
be expanded because I think there are loads of rules that exist only in bits
and bits on the mailing lists. For another I would like to get a patch back
instead of rewritten because without knowing the individual reasons for the
changes its sometimes rather hard to know what the reason for a specific change
was. I do realize thats quite a bit of work for you which is why I hesitated
writing that...

Andres

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2011-05-27 22:10:02 Re: "errno" not set in case of "libm" functions (HPUX)
Previous Message Noah Misch 2011-05-27 21:50:36 Re: Reducing overhead of frequent table locks