From: ericblake@comcast.net (Eric Blake)
To: "It's out in the open!" <cygwin-talk@cygwin.com>
Subject: Re: ssh and SYSTEM
Date: Thu, 29 Jun 2006 00:48:00 -0000 [thread overview]
Message-ID: <062920060048.26483.44A323600006D6280000677322007510900A050E040D0C079D0A@comcast.net> (raw)
> >> >>Nicholas Fong (nfong@xxxxxxxx.xxx) is the person
> >> responsible for those
> I did it because this web site has been the consistent source of
> misinformation for years and I wanted to provide a clear, unambiguous
> place to point people to. No foo at bar dot com. A real email address.
Sounds reasonable to me - anyone silly enough to ask the cygwin
list to clarify third-party information should be pointed instead to
that third-party, which is exactly what you did. We have been trying
(seemingly to no avail) to convince people that the methods at
the pigtail website are simply wrong and/or outdated when it
comes to easily installing ssh on a cygwin system, and that the
documentation that comes with the cygwin port of ssh is the
best source to follow.
>
> I actually checked first to make sure that his email address showed up
> elsewhere on the web.
>
> If people think this is a horrible thing then I'll remove his address
> from the archives but I kind of wanted to have his email address
> archived, too for future reference. But, perhaps I erred in doing this.
Nah - keep it in there. At any rate, I wouldn't remove that post unless
Mr. Fong personally requested it (just like we don't answer to third-party
advice, you shouldn't remove an email address due to third-party
complaints).
>
> I'd be interested in hearing the opinions of the sane members of this
> mailing list.
Oops - I guess that means you can take whatever I said above,
and feed it to the hippos. Is anyone on this list sane?
--
Eric Blake
next reply other threads:[~2006-06-29 0:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 0:48 Eric Blake [this message]
2006-06-29 2:25 ` mwoehlke
2006-06-29 4:28 ` One Angry User
2006-06-29 8:30 ` Corinna Vinschen
2006-06-29 16:27 ` mwoehlke
2006-06-29 16:37 ` Corinna Vinschen
[not found] <03D3B32F0D0D024791C1EE97D087E909075E7F33@EXCH01.purdue.lcl>
[not found] ` <20060628211040.GC20940@trixie.casa.cgf.cx>
[not found] ` <44A2F9B2.5080101@serv.net>
2006-06-28 21:54 ` Christopher Faylor
2006-06-28 23:19 ` Gary R. Van Sickle
2006-06-29 0:35 ` Christopher Faylor
2006-06-29 0:46 ` Igor Peshansky
2006-06-29 0:51 ` Christopher Faylor
2006-06-29 0:50 ` Gary R. Van Sickle
2006-06-29 0:57 ` Christopher Faylor
2006-06-29 1:18 ` Gary R. Van Sickle
2006-06-29 2:15 ` Christopher Faylor
2006-06-29 8:29 ` Corinna Vinschen
2006-06-29 14:53 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=062920060048.26483.44A323600006D6280000677322007510900A050E040D0C079D0A@comcast.net \
--to=ericblake@comcast.net \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).