Re: email addresses

From: Michael Felt <mamfelt(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Mike Landis <mlandis(at)pnmx(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: email addresses
Date: 2010-01-08 04:02:39
Message-ID: 9ade2d511001072002j4685f3a7nec08f19e62f633ad@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

i am learning to use reply all, but having reply go to the list by default,
rather than the last person that replies might be useful as well.

On Thu, Jan 7, 2010 at 4:08 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> On Thu, Jan 7, 2010 at 9:16 AM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
> > Robert Haas escribió:
> >> On Wed, Jan 6, 2010 at 11:13 PM, Mike Landis <mlandis(at)pnmx(dot)com> wrote:
> >> > Can you please stop displaying the email addresses on bug reports?
> It's one
> >> > thing to require an email address - it's another thing entirely to
> publish
> >> > it for spam address harvesting bots.
> >> >
> >> > This is an example page...
> >> > http://archives.postgresql.org/pgsql-bugs/2009-12/msg00092.php
> >>
> >> Eh? I thought we used to obscure emails on these pages. Am I wrong,
> >> or did something get changed?
> >
> > It broke, you complained a couple of months ago, it hasn't been fixed
> > :-( As usual, I can't promise a quick fix but I'll move it to the top
> > of my todo list.
>
> Oh, actually I think it was Bruce that complained, but it was my email
> that was in the example he mentioned.
>
> Our archives are really useful, but the code seems prone to mysterious
> regressions for reasons that are not clear to me.
>
> ...Robert
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Mark Kirkwood 2010-01-08 04:47:26 Re: BUG #5268: PQgetvalue incorrectly returns 0 (corrected)
Previous Message Takahiro Itagaki 2010-01-08 03:15:37 Re: Concurrent update failure in HEAD