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 02:15:00 -0000	[thread overview]
Message-ID: <20060629021532.GA31911@trixie.casa.cgf.cx> (raw)
In-Reply-To: <003101c69b19$f650dca0$020aa8c0@DFW5RB41>

On Wed, Jun 28, 2006 at 08:18:42PM -0500, Gary R. Van Sickle wrote:
>> From: Christopher Faylor
>> Sent: Wednesday, June 28, 2006 7:57 PM
>> To: The Cygwin-Talk Maiming List
>> Subject: Re: ssh and SYSTEM
>> 
>>I'd be interested in hearing the opinions of the sane members of this
>>>>mailing list.
>>
>>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!

Wow.  I should have remembered that you don't follow these things and
been clearer.  I actually was expressing incredulity at your inability to
maintain consistency within the span of two email messages.

Anyway, I really do have the right to ask for opinions from whomever I
see fit and I clearly asked for the opinions of the subset of cygwin
users in this mailing list.

But, yes, I know.  You don't follow.  And, undoubtedly you have an
audience of one who greatly enjoys petulant, confused observations about
what's appropriate for which mailing list so you will be not following
for the foreseeable future.  We all get that by now.

cgf

  reply	other threads:[~2006-06-29  2:15 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
2006-06-29  2:15                 ` Christopher Faylor [this message]
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=20060629021532.GA31911@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).