Mail Archives: cygwin/2008/02/29/18:06:11
Will Parsons wrote:
> I certainly don't *want* to make it inconvenient for potential responders
> - I simply thought that uuencoding was the way one "attached" using the
> nntp interface. If doing so is an annoyance rather than a help, I
> certainly won't do it in the future. What then is the recommendation -
> include it because it's better than no cygcheck output at all, or don't
> bother?
I'd say that including the cygcheck output inline is better than
uuencoding it, even though that tends to be frowned up as it gives lots
of false positives to future archive searchers. But that's just MHO.
> I'm not sure what a pastebin-like site is, but would it really be more
http://pastebin.com/
> convenient for someone to go to a web site to retrieve output than to
> uudecode the mail? (I don't know about the mail reader you use, but
> for me, uudecoding is a couple of keystrokes in slrn - no manual copying
> and pasting required.)
It's most definitely easier for me to click on a URL than to save a
message to a file, switch to a prompt, cd to the directory where I saved
it, fire up an editor, remove the non-uue parts, figure out if I even
have the uudecode program installed, realize that I don't, go install
one, pipe it through uudecode, then finally view the file. It's easy
for you in slrn because that's a newsreader, and uuencoded content in
newsgroups are common. I don't use a newsreader, I use an email client
and uuencoded content in email is fairly rare.
Brian
--
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/
- Raw text -