public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: Re: ssh and SYSTEM
Date: Thu, 29 Jun 2006 00:35:00 -0000	[thread overview]
Message-ID: <20060629003536.GF20940@trixie.casa.cgf.cx> (raw)
In-Reply-To: <002901c69b09$4386da80$020aa8c0@DFW5RB41>

On Wed, Jun 28, 2006 at 06:19:10PM -0500, Gary R. Van Sickle wrote:
>> From: Christopher Faylor
>> Sent: Wednesday, June 28, 2006 4:55 PM
>> To: cygwin-talk at 
>> Subject: Re: ssh and SYSTEM
>> 
>> On Wed, Jun 28, 2006 at 02:50:42PM -0700, L Anderson wrote:
>> >Christopher Faylor wrote:
>> >>On Wed, Jun 28, 2006 at 04:50:26PM -0400, McGraw, Robert P. wrote:
>> >>
>> >>>I am running WinXP SP2
>> >>>
>> >>>I installed openssh and followed the instructions at 
>> >>>http://pigtail.net/LRP/printsrv/cygwin-sshd.html on how to install.
>> >>
>> >>
>> >>Nicholas Fong (nfong@xxxxxxxx.xxx) is the person 
>> responsible for those
>> >                 ^^^^^^^^^^^^^^^^^^
>> >Perhaps a new Cygwin acronym is in order--something like:
>> >
>> >PDPSHFIYR--Please Don't Put Spam Harvester Food In Your Replies.
>> 
>> Of course, it may just be that I meant to do that, too...
>
>???  You are intentionally violating your own rules of the cygwin-at list
>now?  To what possible constructive end?

I'm glad that you asked.  That's why I sent the message here.

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.

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.

I'd be interested in hearing the opinions of the sane members of this
mailing list.

cgf

  reply	other threads:[~2006-06-29  0:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
2006-06-29  0:48 Eric Blake
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

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=20060629003536.GF20940@trixie.casa.cgf.cx \
    --to=cgf-no-personal-reply-please@cygwin.com \
    --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).