public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Gary R. Van Sickle" <g.r.vansickle@worldnet.att.net>
To: <cygwin-talk@cygwin.com>
Subject: RE: ssh and SYSTEM
Date: Thu, 29 Jun 2006 01:18:00 -0000	[thread overview]
Message-ID: <003101c69b19$f650dca0$020aa8c0@DFW5RB41> (raw)
In-Reply-To: <20060629005703.GI20940@trixie.casa.cgf.cx>

> From: Christopher Faylor
> Sent: Wednesday, June 28, 2006 7:57 PM
> To: The Cygwin-Talk Maiming List
> Subject: Re: ssh and SYSTEM
> 
> On Wed, Jun 28, 2006 at 07:50:16PM -0500, Gary R. Van Sickle wrote:
> >1.  Sane members?  Now you *are* posting to the wrong list.
> >2.  Seem that if you're soliciting permission from the 
> Cygwin community 
> >to start editing the cygwin-at mailing list archives, you should be 
> >asking for it on that self-same list, and most certainly not 
> on a list 
> >that primarily concerns itself with the discussion of hippopotomi.
> 
> Wait, so, I was on-topic when I moved here but now I have to 
> go back to the cygwin list to stay on-topic?
> 

So you're just as confused as the rest of us about what the mailing list
rules are, to whom they apply, and to what degree?  Oh dear!

> With one notable exception, the opinions that I'm interested 
> in all reside here.

It's still the wrong list.  Rules is rules Chris, you know that.  Er,
well....

>  And, I specifically moved my response 
> here to short circuit even more inanity regarding pigtail.net.
> 
> And, I wasn't asking permission, I was asking for opinions.
> 

I must have misread.  All apologies.

> Just as an idle question for you Gary:  Have you had a recent 
> head injury?
> 
> Just wondering.
> 
> cgf

How vituperative.  Whatever that means.

But to answer you question: No, I have not suffered a head injury, nor any
serious physical trauma for that matter, recently or otherwise.  Thank you
for your concern though, and rest assured should such an unfortunate event
happen, you will be the first person I notify.  Via the most appropriate and
efficacious channels, of course.

-- 
Gary R. Van Sickle
 

  reply	other threads:[~2006-06-29  1:18 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
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 [this message]
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='003101c69b19$f650dca0$020aa8c0@DFW5RB41' \
    --to=g.r.vansickle@worldnet.att.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).