Re: Not ready for 8.3

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Aidan Van Dyk <aidan(at)highrise(dot)ca>
Cc: Tatsuo Ishii <ishii(at)postgresql(dot)org>, magnus(at)hagander(dot)net, stefan(at)kaltenbrunner(dot)cc, jd(at)commandprompt(dot)com, bruce(at)momjian(dot)us, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Not ready for 8.3
Date: 2007-05-16 15:43:47
Message-ID: 20070516154347.GR4582@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Aidan Van Dyk wrote:
> * Tatsuo Ishii <ishii(at)postgresql(dot)org> [070516 07:23]:
>
> > Maybe. However I think "subject-sequence" has some advantages over
> > Message-Id:
> >
> > - Easy to identify. Message-Id may not appear on some MUA with default
> > setting
> >
> > - More handy than lengthy message Id
> >
> > - Easy to detect messages not delivered, by knowing that the sequence
> > number was skipped
>
> IMNSHO, we should be encouraging lists to move *away* from subject
> munging. Adding more characters into a subject line which can already
> be quite long is just making the situation worse.

+1 on that. It gets worse when messages are crossposted to multiple
lists and so multiple [FOO] strings are put into the subject. On the
other hand I know there is people who remove the [FOO] strings in their
local machines! (I don't do it just because I have been too lazy to
write a procmail rule about it).

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2007-05-16 15:44:10 Re: Not ready for 8.3
Previous Message Neil Conway 2007-05-16 15:40:17 Re: Integer datetimes