public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: mwoehlke <mwoehlke@tibco.com>
To: cygwin-talk@cygwin.com
Subject: Re: No postnews or other Usenet news utilities?
Date: Fri, 26 May 2006 16:07:00 -0000	[thread overview]
Message-ID: <e5759h$u7l$1@sea.gmane.org> (raw)
In-Reply-To: <001b01c6806c$ff6796c0$020aa8c0@DFW5RB41>

Gary R. Van Sickle wrote:
>> From: mwoehlke
>> Gary R. Van Sickle wrote:
>>> 2.  What you claim you want to do is spamming, pure and simple, by 
>>> anybody's definition.  BTW: Anybody's definition is: "Sending 
>>> unsolicited email, usually in an effort to get money from somebody 
>>> legally or otherwise, en masse to a bajillion newsgroups 
>> and/or email addresses."
>>
>> [snip] ...but I think "unsolicited" is at best debatable, if not
>> outright false.
>>
> 
> ?  I don't follow.

Like I said, my impression of *.forsale is that they are like 
classifieds... i.e. EVERYTHING there is advertisement. Therefore, by 
subscribing to such a group, you are stating your intentions to receive 
"junk mail" ("spam"?) targeted to that audience.

>> --
>> Matthew
>> ...Ruthlessly beating Windows with a hammer until it looks like POSIX.
> 
> "Linux".  Cygwin is "Linux" on Windows now.  No, I'm not sure when or why
> that changed either.

But... but... CYNUX! Cygwin's NOT Linux? :-)

I guess it does *look* like Linux, though, but Linux looks like POSIX. 
Since { a => b, b => c } <=> { a => c }, Cygwin looks like POSIX; QED. :-)

http://mathworld.wolfram.com/Transitive.html

-- 
Matthew
Feed the hippo. Love the hippo. Run from the hippo.

  parent reply	other threads:[~2006-05-26 16:07 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <052b01c67f5b$d74ce490$a501a8c0@CAM.ARTIMI.COM>
     [not found] ` <002701c67f73$625804e0$3100000a@microline.mtc>
2006-05-24 22:03   ` mwoehlke
2006-05-25  1:48     ` Bruce Wehr
2006-05-25  3:04       ` Gary R. Van Sickle
2006-05-25 11:24         ` bruce@wehrhere.com
2006-05-26  2:22           ` Gary R. Van Sickle
2006-05-26 22:03             ` Bruce Wehr
2006-05-25 15:20         ` mwoehlke
2006-05-26  2:36           ` Gary R. Van Sickle
2006-05-26  9:27             ` Dave Korn
2006-05-26 16:07             ` mwoehlke [this message]
2006-05-26 16:20               ` Igor Peshansky
2006-05-26 18:38                 ` mwoehlke
2006-05-26 22:54                 ` Bruce Wehr
2006-05-26 23:17                   ` Igor Peshansky
2006-05-26 23:22                   ` Brian Dessent
2006-05-26 23:41                     ` Bruce Wehr
2006-05-27  0:03                       ` Gary R. Van Sickle
2006-05-27  0:07                         ` Igor Peshansky
2006-05-27  0:00                     ` Gary R. Van Sickle
2006-05-26 16:25               ` Dave Korn
2006-05-26 16:43                 ` Dave Korn
2006-05-26 18:54                 ` mwoehlke
2006-05-26 22:44             ` Bruce Wehr
2006-05-25  9:23       ` Owen Rees
2006-05-25  9:44       ` Dave Korn
2006-05-25 15:19       ` mwoehlke
2006-05-25 15:52         ` One Angry User
2006-05-25  2:32 Gary R. Van Sickle
     [not found] <004c01c67fdc$1b0a9990$a501a8c0@CAM.ARTIMI.COM>
2006-05-25 11:10 ` bruce@wehrhere.com
2006-05-25 12:07   ` Dave Korn
2006-05-25 14:31     ` Christopher Faylor
2006-05-26  2:29       ` Gary R. Van Sickle
2006-05-26 22:30     ` Bruce Wehr
2006-05-27  0:22       ` Gary R. Van Sickle
     [not found] <4475E97D.2070204@ateb.com>
2006-05-25 19:20 ` Bruce Wehr

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='e5759h$u7l$1@sea.gmane.org' \
    --to=mwoehlke@tibco.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).