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:[EMAIL PROTECTED]:/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/
|\ _,,,---,,_ [EMAIL PROTECTED]
ZZZzz /,`.-'`' -. ;-;;,_ [EMAIL PROTECTED]
|,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
--- htdocs/bugs.html-orig 2002-10-18 10:50:38.000000000 -0400
+++ htdocs/bugs.html 2002-10-18 10:51:41.000000000 -0400
@@ -87,7 +87,7 @@ using and give the operating system and
"cygwin v1.3.13 under NT 4.0".</li><br>
<li>Run <tt>cygcheck -s -v -r > cygcheck.out</tt> and include that in your
-report.</li><br>
+report as an attachment.</li><br>
<li>Avoid the use of exclamation marks or multiple question marks. They add
nothing to the bug report and provide the impression that you are too excited
to calmly think about the problem.</li><br>
--- src/winsup/doc/how-resources.texinfo-orig 2001-09-07 12:48:23.000000000 -0400
+++ src/winsup/doc/how-resources.texinfo 2002-10-18 11:11:53.000000000 -0400
@@ -86,9 +86,9 @@ is @emph{"it"}?)
Directory install? If the former, exactly when and from what mirror?
If the latter, which packages did you download? Which version of
setup.exe? Any subsequent updates?)
-@item Details about your Cygwin setup, accomplished by @emph{pasting}
-the output of 'cygcheck -s -v -r' into your message. (Do not send the
-output as a file attachment.)
+@item Details about your Cygwin setup, accomplished by @emph{attaching}
+the output of 'cygcheck -s -v -r' to your message. (Do not paste the
+output into the message.)
@item A valid return address, so that a reply doesn't require manual editing of
the 'To:' header.
@end itemize
--
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/
