git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Elijah Newren <newren@gmail.com>, Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Felipe Contreras <felipe.contreras@gmail.com>
Subject: RE: Contributions which I feel are dangerous and/or deceptive (Was: Re: What's cooking in git.git (Jun 2021, #06; Thu, 17))
Date: Thu, 17 Jun 2021 09:19:46 -0500	[thread overview]
Message-ID: <60cb5a02f1b31_1259c2086f@natae.notmuch> (raw)
In-Reply-To: <CABPp-BG53Kd7MhzE3hdq5fjBQVV2Ew3skcUCAuTfM5daP2wmZA@mail.gmail.com>

Elijah Newren wrote:
> I hate doing this, but...
> 
> On Wed, Jun 16, 2021 at 7:58 PM Junio C Hamano <gitster@pobox.com> wrote:
> 
> > * fc/pull-cleanups (2021-06-15) 3 commits
> >  - pull: trivial whitespace style fix
> >  - pull: trivial cleanup
> >  - pull: cleanup autostash check
> >
> >  Code cleanup.
> >
> >  Will merge to 'next'.
> 
> Please don't.
> 
> Let me quote from four recent emails, three of which will look
> unrelated at first, and then I'll tie it together:

This is called an ad hominem attack: you are attacking the person
submitting the patches, not the patches themselves.

Do you see anything wrong with these particular patches?

You are mentioning another completely unrelated thread with completely
unrelated patches. I already said I did my best on that other thread,
and I wished you good luck with those patches.

Now you are coming here to personally attack me. This is harassment,
and it goes against the code of conduct.


These are examples of what constitutes positive behavior:

  * Demonstrating empathy and kindness toward other people

This is definitely not happening from you.

  * Being respectful of differing opinions, viewpoints, and experiences

You are disrespecting a differing opinion.

  * Giving and gracefully accepting constructive feedback

You are not giving constructive feedback.

What do you want me to do with the 3 patches above? Be constructive.

  * Accepting responsibility and apologizing to those affected by our mistakes,
    and learning from the experience

I believe your personal attacks merit an apology, but I'm not even going
to request that, all I wish is that you focus on the patches at hand.

  * Focusing on what is best not just for us as individuals, but for the
    overall community

You are not doing this either. Forget about me and think about the
community. Do you see the patches above helping or hindering the
community?

If they hinder, please state how, and I'll fix them.


Examples of **unacceptable** behavior:

  * Trolling, insulting or derogatory comments, and personal or political attacks

This is a personal attack: it's directed towards me, not the patches.

  * Public or private harassment

This is public harassment.


I have a pretty thick skin, and I rarely do use my emotions for the
basis of anything, but your personal attacks are draining me
emotionally. I receive personal attacks in a multitude of media, but I
did not expect them on the git mailing list, and especially not from
you.

I have no problem soldiering through personal attacks if doing so is
going to result in a better outcome, in this case better patches. But I
don't see any better outcome on the horizon. These personal attacks are
gratuitous.

Once again, please focus on the patches, and I'll be happy to address
any and all of your concerns.

Cheers.

-- 
Felipe Contreras

  reply	other threads:[~2021-06-17 14:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17  2:55 What's cooking in git.git (Jun 2021, #06; Thu, 17) Junio C Hamano
2021-06-17  9:38 ` jh/builtin-fsmonitor, was " Johannes Schindelin
2021-06-17  9:40 ` js/subtree-on-windows-fix, " Johannes Schindelin
2021-06-17 12:38 ` Contributions which I feel are dangerous and/or deceptive (Was: Re: What's cooking in git.git (Jun 2021, #06; Thu, 17)) Elijah Newren
2021-06-17 14:19   ` Felipe Contreras [this message]
2021-06-17 15:06     ` Elijah Newren
2021-06-17 16:58       ` Felipe Contreras
2021-06-17 14:42 ` What's cooking in git.git (Jun 2021, #06; Thu, 17) Felipe Contreras
2021-06-17 23:58 ` brian m. carlson
2021-06-18  0:27   ` Jeff King
2021-06-18  4:28     ` Felipe Contreras
2021-06-19  7:18     ` Junio C Hamano
2021-06-19 17:27       ` Ignoring valid work Felipe Contreras
2021-06-18  4:20   ` What's cooking in git.git (Jun 2021, #06; Thu, 17) Felipe Contreras
2021-06-18 16:32 ` Jeff Hostetler
2021-06-25 22:21 ` Emily Shaffer
2021-06-25 22:26   ` Randall S. Becker
2021-06-28 16:46   ` Jeff Hostetler

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=60cb5a02f1b31_1259c2086f@natae.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=newren@gmail.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 NNTP newsgroup(s).