Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Cc: Subject: RE: cygwin digest format Date: Wed, 9 Feb 2005 14:31:51 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <4209C187.4060204@sun.ac.za> Message-ID: X-OriginalArrivalTime: 09 Feb 2005 14:31:51.0597 (UTC) FILETIME=[1862FDD0:01C50EB4] > -----Original Message----- > From: cygwin-owner On Behalf Of Gorden Jemwa > Sent: 09 February 2005 07:54 > To: cygwin [ X-post to -talk list; I think we should TITTTL if the discussion becomes any prolonged. ] > Could the digest format be changed into a single message format > containing all the messages instead of a single message with other > messages embeddded as attachments? I don't know what others think but > IMO its easier to read browse through a single message than opening > individual attachment, unless (of course) there are strong reasons for > the current digest format. I can think of a couple of immediate advantages: 1) If you reply to a digest, the References or In-Reply-To headers will point to the digest, rather than the item you're actually replying to, which breaks the threading. Sending the posts as individual items means people will reply to the one they actually want to reply to. And the Subject line will be set correctly too. 2) We never get idiots sending 1 line top-posted replies with quoted copies of the entire preceding day's traffic below. Item 1) may be important to some people, but it's 2) that particularly matters to me! cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/