Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <5.1.0.14.2.20021015100200.02f9c928@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
Date: Tue, 15 Oct 2002 10:12:32 -0700
To: cygwin <cygwin AT cygwin DOT com>
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: Improving List Archive Searching
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi,

I would like to suggest and request that "cygcheck -s" output not be 
included in the body of postings to the Cygwin mailing list. Because that 
output includes a list of packages, DLLs and key executables, including it 
in the body of a message can cause many false hits when searching the list 
archives for message pertinent to a particular program, package or library. 
For this reason, I believe it's distinctly preferable to place that output 
in an attachment.

Perhaps when cygcheck output is solicited in pursuit of a problem diagnosis 
the person requesting that output could include a reminder of the 
preference for placing that output in an attachment?

I don't think this is the sort of thing to enforce the way UCE is blocked 
and that merely suggesting this change in practice won't eliminate it even 
if everyone were to agree, but if we could start to shift the general 
practice regarding posting of cygcheck output to one of preferring 
attachments, it would improve the "signal-to-noise" ratio for those putting 
in the effort of searching for answers already extant in the list archives 
before posting.

Randy 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/