From: Yitzchak Scott-Thoennes <sthoenna@efn.org>
To: cygwin-talk@cygwin.com
Subject: Re: Serious performance problems (malloc related?)
Date: Tue, 31 May 2005 03:48:00 -0000 [thread overview]
Message-ID: <20050529174049.GB1304@efn.org> (raw)
In-Reply-To: <20050528064031.GA12112@trixie.casa.cgf.cx>
On Sat, May 28, 2005 at 02:40:31AM -0400, Christopher Faylor wrote:
> On Fri, May 27, 2005 at 09:29:54PM -0700, Edward Peschko wrote:
...
> For the record: I do not give any serious consideration to the two or
> three email voices here who think they speak from some sort of moral
> high ground and are compelled to tell me how to communicate. I do very
> much appreciate that you haven't lapsed into profanity or sarcasm,
> however.
>
> 99% of the time when people report a problem they are saying "I have a
> problem. I didn't go to too much effort to figure it out. I didn't do
> any research about how I should report it. I want you to help me now."
> My response to this kind of email is normally to point people to where
> they need to go to either fix the problem themselves or provide the
> information that we need to fix the problem. If people don't like the
> way I do this, here's something that should be obvious by now: I don't
> care. You can take my response or leave it.
>
> In this case, the OP provided a test case, which is rare (and
> appreciated). They didn't provide any other details other than that,
> although he did offer noise information about how he'd rather be using
> linux and how this was a serious problem. He also offered a completely
> uninformed guess.
>
> We normally ask for the guidelines from http://cygwin.com/problems.html,
> to be followed, however, I know that issues of performance are rarely
> cut and dry (although knowing the version of cygwin that was exhibiting
> problems would have been interesting) and so the real key here is to
> learn enough about the DLL to diagnose the problem.
>
> What you interpret as "snippiness" is just cut and dry advice: If you
> have a lot of people relying on a product and the product is misbehaving
> then it makes sense to either purchase support or learn enough about it
> so that you can support it. Relying on volunteer email to fix something
> which is impacting your whole organization is not a reliable way to get
> "serious problems" fixed.
>
> FWIW, the original message violated many of the tenants of Eric Raymond's
> "How to Ask Smart Questions" and I responded just like Eric Raymond
> predicted.
>
> >There are two ways of seeing it - everybody (or a huge subset of everybody)
> >is wrong and I'm squeaky clean, or yes I could improve my attitude in how
> >to deal with people.
>
> One thing you may notice in my email, is that I normally try to I try to
> tell people what they need to do to get results. I don't normally tell
> people that "everyone" thinks a certain way and I don't often make
> personal observations about people's character. I just offer (often
> terse) advice on what I think someone should do to solve a problem.
>
> As it turns out, for the most part, the way that I conduct myself
> provides me with the results that I want. The mailing list is fairly
> self policing these days. People who report "cygwin not work" bugs are
> directed towards the right way to report a problem and, often, their
> problems are fixed. People who want to contribute are pointed at
> cygwin-apps or cygwin-patches and often they end up contributing.
>
> Other people who want to change things but don't have a clear idea about
> what they want to do and only know that they are angry because I'm not
> nice to them, and won't give their half-formed thoughts the
> consideration they know they deserve, eventually go away. Which is
> exactly what I want to happen.
>
> This isn't a democracy. It's just a successful free software project.
> I (and Corinna) get to make the rules and I (we) get to comport myself
> how I (we) see fit. If you don't like that then you can take cygwin
> source code and make your own fork.
>
> (And, boy will I be fuming. That should offer some incentive at least)
>
> >I know this cultural issue has deterred me in the past; I keep hoping that
> >things'll change and I (and possibly many others) would change their mind
> >and start assisting cygwin.
>
> I have to confess that I'm *glad* that you are deterred. IIRC, in your
> communication to the cygwin list you rarely demonstrated a real grasp of
> the technical issues that you were trying to grapple with. So, I'm
> happy not to have to either witness or correct your misperceptions on a
> regular basis.
>
> Oh, and, there you go again. First it was "everyone" and then it was
> "possibly many others". I believe that this argument style is called
> "Appeal to Belief". You've posted relatively rarely to the cygwin list
> and have never, as I mentioned, and as I recall, demonstrated any
> particularly strong grasp of either the technical or community aspects
> of cygwin so I don't accept your premise that you speak for "everybody"
> or "possibly many others".
>
> Not that it would matter if I did.
IMO there should be a link to this message from
http://cygwin.com/acronyms/#WJM.
Comments?
next prev parent reply other threads:[~2005-05-29 17:40 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4297A14B.9070409@plausible.org>
[not found] ` <20050527234027.GA7522@trixie.casa.cgf.cx>
[not found] ` <4297B572.9050200@plausible.org>
[not found] ` <20050528005054.GB7522@trixie.casa.cgf.cx>
[not found] ` <20050528042954.GA4196@venus>
2005-05-29 16:07 ` Christopher Faylor
2005-05-31 3:48 ` Yitzchak Scott-Thoennes [this message]
[not found] ` <20050528131501.V53507@logout.sh.cvut.cz>
[not found] ` <20050528160424.GB12395@trixie.casa.cgf.cx>
2005-05-29 17:03 ` Yitzchak Scott-Thoennes
2005-05-29 17:30 ` Christopher Faylor
2005-05-29 17:40 ` Yitzchak Scott-Thoennes
2005-05-31 16:53 ` Dave Korn
2005-05-31 17:40 ` Christopher Faylor
2005-05-31 17:43 ` Dave Korn
2005-05-31 17:47 ` Dave Korn
2005-05-31 18:03 ` Yitzchak Scott-Thoennes
2005-05-31 19:16 ` Dave Korn
2005-06-01 8:55 ` Yitzchak Scott-Thoennes
2005-05-31 19:47 ` Christopher Faylor
2005-05-31 18:08 ` Igor Pechtchanski
2005-05-31 3:49 Gary R. Van Sickle
[not found] <20050528174537.GA2593@trixie.casa.cgf.cx>
[not found] ` <20050531031611.7D83013C9D9@cgf.cx>
2005-05-31 4:15 ` Christopher Faylor
2005-05-31 4:29 Gary R. Van Sickle
[not found] <20050531034844.46A4713C9D9@cgf.cx>
2005-05-31 4:31 ` Christopher Faylor
[not found] <20050531041503.ABDB513C9D9@cgf.cx>
2005-05-31 4:59 ` Christopher Faylor
2005-05-31 9:12 Gary R. Van Sickle
[not found] <20050531034845.C15911703A4@samwise.efn.org>
2005-05-31 16:16 ` Yitzchak Scott-Thoennes
2005-05-31 20:14 ` Gary R. Van Sickle
[not found] ` <20050531195822.A96441701DA@samwise.efn.org>
2005-05-31 20:44 ` Yitzchak Scott-Thoennes
2005-06-01 0:29 ` Gary R. Van Sickle
[not found] ` <20050601001618.641C8170217@samwise.efn.org>
2005-06-01 11:00 ` Yitzchak Scott-Thoennes
[not found] <20050531045912.409FE13C9D9@cgf.cx>
2005-05-31 16:53 ` Christopher Faylor
2005-05-31 19:58 ` Gary R. Van Sickle
[not found] ` <20050531194715.5E13513C9D9@cgf.cx>
2005-05-31 20:21 ` Christopher Faylor
2005-05-31 20:42 ` Gary R. Van Sickle
2005-05-31 21:27 ` Yitzchak Scott-Thoennes
2005-05-31 21:38 ` Christopher Faylor
2005-06-05 1:25 ` Linda W
2005-06-06 0:40 ` Charles Wilson
[not found] ` <20050531202146.A305D13C9D9@cgf.cx>
2005-05-31 23:39 ` Christopher Faylor
2005-06-01 0:02 ` Gary R. Van Sickle
[not found] ` <20050531233916.62E6213C9D9@cgf.cx>
2005-06-01 8:43 ` Christopher Faylor
2005-06-01 19:38 ` Gary R. Van Sickle
[not found] ` <20050531194716.42466170417@samwise.efn.org>
2005-05-31 20:44 ` Yitzchak Scott-Thoennes
2005-06-01 2:12 ` Gary R. Van Sickle
[not found] <NUTMEGpFVjCRGryWtII00000882@NUTMEG.CAM.ARTIMI.COM>
2005-06-01 0:16 ` Dave Korn
2005-06-01 0:31 ` Gary R. Van Sickle
2005-06-01 16:18 ` Lionel B
2005-06-01 16:23 ` One Angry User
2005-06-01 19:29 ` Christopher Faylor
2005-06-01 20:01 Gary R. Van Sickle
[not found] <200506011930.j51JTx1w010465@mx.cims.nyu.edu>
2005-06-02 2:08 ` One Angry User
[not found] <20050601192617.349C156E5@mail.hq.astra.ph>
2005-06-02 2:49 ` Carlo Florendo
2005-06-02 3:26 ` Gary R. Van Sickle
[not found] <20050602024610.10D13A32A@mail.hq.astra.ph>
2005-06-02 3:29 ` Carlo Florendo
2005-06-02 3:56 ` Gary R. Van Sickle
[not found] <20050531233537.3FE6B669B@mail.hq.astra.ph>
2005-06-02 3:49 ` Carlo Florendo
2005-06-02 3:58 ` Gary R. Van Sickle
[not found] ` <20050602035615.48B4213C08A@cgf.cx>
2005-06-02 16:00 ` Christopher Faylor
[not found] <20050602034611.4A0ACA843@mail.hq.astra.ph>
2005-06-02 4:04 ` Carlo Florendo
[not found] <20050602035232.CEA8471B5@mail.hq.astra.ph>
2005-06-02 12:57 ` Carlo Florendo
2005-06-02 13:14 ` Fred Kulack
2005-06-02 13:19 ` Dave Korn
2005-06-02 15:17 ` Christopher Faylor
2005-06-02 16:31 ` Igor Pechtchanski
2005-06-02 19:44 ` Dave Korn
2005-06-02 16:13 ` Igor Pechtchanski
[not found] <3D848382FB72E249812901444C6BDB1D03E04FD3@exchange.timesys.com>
[not found] ` <20050602190022.GG6597@trixie.casa.cgf.cx>
2005-06-02 19:50 ` Shankar Unni
2005-06-02 19:56 ` Christopher Faylor
2005-06-02 20:21 ` Igor Pechtchanski
2005-06-02 20:28 ` Christopher Faylor
2005-06-02 20:30 ` Yitzchak Scott-Thoennes
2005-06-02 20:53 ` One Angry User
2005-06-02 20:56 ` Christopher Faylor
2005-06-02 21:02 ` Christopher Faylor
2005-06-03 9:40 ` One Angry User
2005-06-03 13:26 ` Dave Korn
2005-06-04 22:23 ` One Angry User
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=20050529174049.GB1304@efn.org \
--to=sthoenna@efn.org \
--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).