From: Amit Choudhary <amitchoudhary0523@gmail.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Your toxic comments.
Date: Sun, 13 Jun 2021 19:28:19 +0530 [thread overview]
Message-ID: <CAFf+5zijXiU8b18UyCBVGboc41L3POBDT8kYH3Rm+YsVZi21Nw@mail.gmail.com> (raw)
In-Reply-To: <567aefb8-3769-72de-146f-7c45ab54ad12@gotplt.org>
I am done with all this now. I am not going to respond to your comments.
I am starting a new job from tomorrow which is paying me $150,000 per anum
for writing 4G / 5G code which the whole world will use in a few months.
Need to write code for balanced b-trees for my new job and code for eNB
node.
I would better focus on that now.
Amit
On Sun, Jun 13, 2021, 7:16 PM Siddhesh Poyarekar <siddhesh@gotplt.org>
wrote:
> On 6/13/21 2:28 PM, Amit Choudhary wrote:
> > There I read that you failed to qualify for IIT (twice) and you went
> > into a year long depression.
> >
> > This means that you are not a very intelligent person.
> >
> > I had passed IIT JEE exam and did Computer Science from IIT-Varanasi.
> >
> > This means that I am more intelligent than you.
>
> OK, PM me your mailing address I'll mail you a t-shirt that says that :)
>
> On 6/13/21 5:26 PM, Amit Choudhary wrote:
> > Siddhesh started all this by making stupid comments. I will write here
> > what he wrote:
>
> I don't think you deserve an explanation of my review guidelines from me
> after the vile personal attack you launched on me. In fact, most of
> them are reiterations of what other reviewers have said in the past but
> you either haven't read them or haven't understood them. But don't
> worry, those comments are mostly targeted at other reviewers who (if
> they choose to endure your conversation style) may choose to engage with
> you.
>
> > ==============
> >
> > At this point, just before Siddhesh sent his meaningless mail,
> > everything was coming on track. I sent results, and Paul asked me to
> > improve my algorithm and things were taking shape. But then Siddhesh's
> > email derailed it all.
>
> It was not 'coming on track' and my intervention was necessary because
> (1) as one of the maintainers of glibc it is my responsibility to
> reiterate the review standards for the project when I see gaps and (2)
> you've been misinterpreting the politeness of the community members as
> compliance. You would have run into all those issues later even if I
> had not iterated them. You literally expressed surprise at a couple of
> them as if they weren't mentioned in the thread before.
>
> Finally, this is my last email to you until you are more respectful in
> your language.
>
> Siddhesh
>
next prev parent reply other threads:[~2021-06-13 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 8:58 Amit Choudhary
2021-06-13 10:51 ` Adhemerval Zanella
2021-06-13 11:05 ` Amit Choudhary
2021-06-13 11:16 ` Adhemerval Zanella
2021-06-13 11:56 ` Amit Choudhary
2021-06-13 13:46 ` Siddhesh Poyarekar
2021-06-13 13:58 ` Amit Choudhary [this message]
2021-06-13 14:07 ` Amit Choudhary
2021-06-13 14:19 ` Unacceptable behaviour by Amit Choudhary Dmitry V. Levin
2021-06-14 19:02 ` Carlos O'Donell
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=CAFf+5zijXiU8b18UyCBVGboc41L3POBDT8kYH3Rm+YsVZi21Nw@mail.gmail.com \
--to=amitchoudhary0523@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).