public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Linda Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: Too many mailing lists(passing the buck)
Date: Sun, 22 Jun 2014 21:22:00 -0000	[thread overview]
Message-ID: <53A748ED.8060609@tlinx.org> (raw)
In-Reply-To: <20140621115148.GB17140@dinwoodie.org>

Adam Dinwoodie wrote:
> On Fri, Jun 20, 2014 at 03:07:37PM -0600, Warren Young wrote:
>   
>> Every time someone says "That's not on topic here, go elsewhere," it
>> can easily be read as "Go away."  The Cygwin project should only be
>> pushing away toxic people, and multiple mailing lists do not have
>> that happy side effect.
>>     
>
> I've never seen a reply saying "that's not on topic here, go away" that
> could be read as you describe.  
----
   You didn't even bother to check google?
i settled on looking at bash:
bash cygwin "off-topic" -stackoverflow

But have seen similar for X11 related.

on the first page: (all talking about the topic being wrong for the list 
involved).
 
https://cygwin.com/ml/cygwin/2003-12/msg00252.html
https://cygwin.com/ml/cygwin/2001-03/msg00691.html
https://cygwin.com/ml/cygwin/2008-11/msg00423.html
https://cygwin.com/ml/cygwin/2013-02/msg00343.html


vs. the opposite problem where a cygwin devel yanked my prob
from a cp-bug-report and closed it:

bug was related to a case-bug using cp -a and being
told it was a cygwin bug unless I could recreate it
on linux (even though the bad code was in 'cp'.)

(had to do with ignoring case, and creating it with a case
ignoring FS on linux would have been too much of a pain
(like XFS has such an option) .

project owners constantly like to pass the buck in hopes the
user will give up...usually project owners win because reporting
bugs is too much trouble.




--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2014-06-22 21:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 21:07 Too many mailing lists Warren Young
2014-06-20 23:25 ` Steven Penny
2014-06-21 11:52 ` Adam Dinwoodie
2014-06-22 21:22   ` Linda Walsh [this message]
2014-06-22 21:38     ` Too many mailing lists(passing the buck) Christopher Faylor
2014-06-23  1:10       ` Larry Hall (Cygwin)
2014-06-23  3:42         ` Christopher Faylor
2014-06-23 17:55   ` Too many mailing lists Warren Young
2014-06-22  1:35 ` Andrey Repin
2014-06-23 18:45   ` Warren Young
2014-06-23 19:47     ` Cliff Hones
2014-06-25  0:20     ` Andrey Repin
2014-06-23 14:53 ` Eric Blake
2014-06-26  0:54 ` KIMURA Masaru

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=53A748ED.8060609@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=cygwin@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).