From: Borislav Petkov <bp@alien8.de>
To: "Francesca V." <feaeressea@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Speaking out against Sarah Sharp
Date: Wed, 24 Jul 2013 12:33:56 +0200 [thread overview]
Message-ID: <20130724103356.GC30932@pd.tnic> (raw)
In-Reply-To: <CAAse1WDN_ghcehSnT=P5YOR=HqAzEiNoB7-f8hdifjhk1V2jsg@mail.gmail.com>
On Wed, Jul 24, 2013 at 03:49:19AM -0600, Francesca V. wrote:
> Sarah Sharp recently posted a tirade about verbal abuse on here and
> her blog - where she dismisses all comments disagreeing with her as
> being from trolls, and deletes them - and takes pride in being
> "accidentally racist", when she's not attention-whoring on the LKML.
>
> I want to say, as a female developer: Sarah Sharp is not
> representative of us. She's not representative of the women at Intel.
> She's not representative of women in technology.
>
> She's a bully. She bullies her husband. She dismisses bullying of her
> coworkers. (Google: 'intel kick me'). And she's trying to bully Linus.
>
> I know he's a big boy. But dare I say, Linus is too nice to tell this
> drama queen to bugger off.
>
> No one was talking to her. Linus' 'Shut the fuck up' was to a
> developer who refused to take responsibility for his code, and blamed
> someone else's code. It was deserved criticism. Then, Linus went and
> explained just that:
>
> "Similarly, you will see fireworks if some long-term maintainer makes
> excuses for breaking user space etc. That will make me go into
> incoherent rages."
>
> Which is exactly what the emails held up as "verbal abuse" show.
>
> Sarah's exclaiming how she won't take any of this abuse, yet no one
> was directing any of it at her. It's sickening she's got nothing
> better to do then stick her nose in and decide to dictate to her
> betters how to behave. Yes I said her betters: We all run Linux. Not
> Sarax.
>
> Sarah justifies pissing in the Linux sandbox because Intel 'pays her'
> to develop kernel drivers. Perhaps her direct manager might rethink
> this decision in light of how she's representing Intel in her "off"
> time.
>
> To Linus: You're a hero to many of us. Don't change. Please. You DO
> NOT need to take time away from doing code to grow a pair of breasts
> and judge people's emotional states:
>
> "It does not matter if your cursing fits have causes. The fact is that
> if you misjudge someone's emotional state for the day, you yelling at
> them is not productive."
>
> As a woman, I couldn't be silent and stand by while Sarah bullied and
> assaulted this list with her profanity and self-indulgent narcissism.
> She's the problem. Not you. Not your style of communication. We
> technical women appreciate being treated equally by our male peers,
> with blunt directness and unambiguous criticism. We are not fragile
> flowers.
I don't know if you're for real but if you are, you just hit the nail on
the head!
I only wish this would've come earlier and put a timely end to this
kindergarten bullshit.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2013-07-24 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAse1WDGbvt5zLTS60VbLvr396rM-DxKf=8WhML+eueKkqDmWQ@mail.gmail.com>
2013-07-24 9:49 ` Francesca V.
2013-07-24 10:33 ` Borislav Petkov [this message]
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=20130724103356.GC30932@pd.tnic \
--to=bp@alien8.de \
--cc=feaeressea@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome