Re: [PATCH 3/3] Document geqo_seed variable.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bernd Helmle <mailings(at)oopsware(dot)de>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH 3/3] Document geqo_seed variable.
Date: 2009-07-15 17:01:05
Message-ID: 603c8f070907151001u24f27d87k4953f64e3bd8130a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 15, 2009 at 10:13 AM, Bernd Helmle<mailings(at)oopsware(dot)de> wrote:
> --On 15. Juli 2009 08:06:48 +0200 Andres Freund <andres(at)anarazel(dot)de> wrote:
>
>> It should not create multiple threads I think as all messages were a
>> response  the first mail?
>
> It does (at least my MUA understood that correctly), but since many people
> are reading in a "backlog"-style manner, i have to agree with Robert. It
> makes it a little bit harder to track all changes which are intended by a
> specific discussion.

Gmail starts a new thread if the subject line is changed, but I'm not
going to hold the entire world hostage to my preferred email client.
There are other problems, too, like if I want to apply this patch I
have to download multiple emails to do it, and multiple links have to
be added to the CommitFest app to reference the different parts.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2009-07-15 17:13:36 Re: [PATCH 3/3] Document geqo_seed variable.
Previous Message Nagy Karoly Gabriel 2009-07-15 16:59:56 Re: Add encoding support to COPY