This is the mail archive of the
mailing list for the Cygwin project.
Re: announcements trapped by anti-viral filter
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- To: CU List <Cygwin at Cygwin dot Com>
- Date: Mon, 07 Jan 2002 11:32:03 -0500
- Subject: Re: announcements trapped by anti-viral filter
- References: <3C39C96C.18F95156@yahoo.com>
- Reply-to: CU List <Cygwin at Cygwin dot Com>
> Subject: Re: announcements trapped by anti-viral filter
> Date: Mon, 7 Jan 2002 08:03:19 -0800 (PST)
> From: Joshua Franklin <email@example.com>
> To: firstname.lastname@example.org
> Well, I guess I'll post this to the cygwin list then.
> I thought the whole point of a mailing list was to
> have a place where people could get a problem solved
> and others can search for the same problem later.
> I knew of a way around a stupid corporate virus
> So, I posted to the original list and CC'd the
> poster. I thought it might be confusing to someone
> searching the archives to find a message on
> cygwin-apps with no reply.
It's common courtesy to keep OT off list. If you respond to an OT then
don't include the list in the response. If you think it's pertinent for
list members the email@example.com is the place to post that. All other
lists must remain per specified topic or the quality of developer time
will be diminished. It seems that cygwin-apps posts tend to be a big
offender of OT posts. Please review the http://cygwin.com/lists.html
page before posting to it or other lists. We don't want
firstname.lastname@example.org to become YA email@example.com.
The primary purpose of cygwin-apps is for maintainers of cygwin
distributed applications to communicate with one another. It's not for
posting questions about the operation of the application. If you're not
maintaining an application then you're safe post will be to
firstname.lastname@example.org not to email@example.com.
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html