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 X-Originating-IP: [195.92.67.72] From: "Elfyn McBratney" To: References: Subject: Re: [PATCH] Re: Improving List Archive Searching Date: Fri, 18 Oct 2002 16:40:47 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Message-ID: X-OriginalArrivalTime: 18 Oct 2002 15:41:47.0642 (UTC) FILETIME=[DE5DE5A0:01C276BC] Igor, the password for the cvs server is anoncvs... Elfyn ----- Original Message ----- From: Igor Pechtchanski To: Randall R Schulz Cc: Sent: Friday, October 18, 2002 4:30 PM Subject: [PATCH] Re: Improving List Archive Searching > On Tue, 15 Oct 2002, Randall R Schulz wrote: > > > 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 > > I agree with the sentiment, and I guess other people do too, since I've > noticed a lot of new messages explicitly mentioning the attachment. > However, the FAQ and the bug reporting page need to be updated, as people > looking there receive conflicting instructions. Attached are patches to > bugs.html and src/winsup/doc/how-resources.texinfo. The FAQ will need to > be regenerated once the second patch is applied. The patches will > probably need to be applied to different CVS subtrees, sorry. Oh, and > they probably don't need ChangeLog entries, do they? > > On a separate note, I wasn't able to check out the cygwin webpages using > anoncvs, so I had to use WebCVS and wget. I tried 'cvs -d > :pserver:anoncvs AT sources DOT redhat DOT com:/cvs/cygwin checkout htdocs', and the > error I got was > > cvs checkout: authorization failed: server sources.redhat.com rejected access to /cvs/cygwin for user anoncvs > cvs checkout: used empty password; try "cvs login" with a real password > > It's not essential that I'm able to check this out, but it would be good > to know whether I'm doing it right or I've screwed up somewhere. > Igor > -- > http://cs.nyu.edu/~pechtcha/ > |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu > ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com > |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski > '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! > > "Water molecules expand as they grow warmer" (C) Popular Science, Oct'02, p.51 > ---------------------------------------------------------------------------- ---- > -- > 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/ -- 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/