Re: [PATCH 3/3] Document geqo_seed variable. - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [PATCH 3/3] Document geqo_seed variable.
Date
Msg-id 200907151913.37041.andres@anarazel.de
Whole thread Raw
In response to Re: [PATCH 3/3] Document geqo_seed variable.  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wednesday 15 July 2009 19:01:05 Robert Haas wrote:
> On Wed, Jul 15, 2009 at 10:13 AM, Bernd Helmle<mailings@oopsware.de> wrote:
> > --On 15. Juli 2009 08:06:48 +0200 Andres Freund <andres@anarazel.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.
For me its easier, as the different discussions are kept separate...

> 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.
Referencing the top Mail seems enough for me. To apply patches from mail I 
have setup a filter which can apply an mbox directly...

But as patches I send are not intended to be consumed by me, I will stop 
sending patches like that ;-)

Andres

PS: Gmail is a strange beast.


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PATCH 3/3] Document geqo_seed variable.
Next
From: Böszörményi Zoltán
Date:
Subject: Split-up ECPG patches