git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Felipe Contreras <felipe.contreras@gmail.com>
Subject: 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 05:38:24 -0700	[thread overview]
Message-ID: <CABPp-BG53Kd7MhzE3hdq5fjBQVV2Ew3skcUCAuTfM5daP2wmZA@mail.gmail.com> (raw)
In-Reply-To: <xmqqr1h1mc81.fsf@gitster.g>

Hi,

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:

From https://lore.kernel.org/git/CABPp-BGrKjpjb5epv1nXcvn4Z1OHP4Uf6G1f9FARmwUcFVa96Q@mail.gmail.com/
:
(a quote of mine to Felipe)
"""
You clearly have talent.
With regards to the zdiff3 patches, I've stated above why I think you
haven't done your due diligence.  Sometimes people make mistakes;
that's something that can be corrected.  What I find egregious here is
that even when Peff and I have pointed out how more due diligence is
expected and needed, you've dug in to explain why you think your
course of action was reasonable (both here and in
https://lore.kernel.org/git/60c82a622ae66_e5292087f@natae.notmuch/).
That in my mind raises your submissions from careless to glaringly
cavalier.  Further, it makes me suspect we may continue to see you
repeat such behavior.  That worries me.
"""

From https://lore.kernel.org/git/CABPp-BEXtJtkkh9Diuo4e1K1ci=vggGxkLRDfkpOH12LM8TCfA@mail.gmail.com/
:
(another quote of mine to Felipe)
"""
...you
are willing to eschew what I view as even the most basic of
responsibilities in ensuring you are submitting valid patches, and
even worse, you are unwilling to change how you approach the project
even when those are pointed out to you.
"""

From https://lore.kernel.org/git/YMhx2BFlwUxZ2aFJ@coredump.intra.peff.net/ :
(a quote from Peff to Felipe)
"""
But much more important, in my opinion: that you would dismiss without
further investigation a report of a bug from the one person who actually
had experience running with the patch implies a level of carelessness
that I'm not comfortable with for the project.

I had already given up on having substantive discussion with you, but I
had hoped I could help the project by pointing out relevant facts in
areas that you were working in. But if a simple statement like "this
segfaulted for me" is not even useful, then I don't see much point in
communicating with you at all.
"""

From https://lore.kernel.org/git/60c887f678c88_e63320846@natae.notmuch/ :
(a quote from Felipe responding to me)
"""
> * `Reviewed-by:`, unlike the other tags, can only be offered by the
>   reviewer and means that she is completely satisfied that the patch
>   is ready for application.  It is usually offered only after a
>   detailed review.

Yeah, I read that after I sent v3. In this series I simply cherry-picked
it from a previous series.
"""

The first three quotes highlight what I feel is a reckless submission
from Felipe; from the threads you can read in the linked messages, I
believe he sees no problems in his approach and appears intent to
continue that course in the future.

But the fourth raises the alarm levels for me further.  In the fourth
quote, Felipe admits to having learned what "Reviewed-by" meant, then
cherry-picked a patch of his own with an inappropriate Reviewed-by and
resubmitted it anyway.  And he did not resubmit the series with the
error corrected when it was raised to his attention.  That feels
deceptive to me.

If I were in charge, at this point I would drop all of Felipe's
patches on the floor (not just the ones from these threads), and not
accept any further ones.  I am not in charge, though, and you have
more patience than me.  But I will not be reviewing or responding to
Felipe's patches further.  Please do not trust future submissions from
him that have an "Acked-by" or "Reviewed-by" from me, including
resubmissions of past patches.

I will allow Felipe to have the last word if he so chooses; I won't
respond further.

  parent reply	other threads:[~2021-06-17 12:39 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 ` Elijah Newren [this message]
2021-06-17 14:19   ` Contributions which I feel are dangerous and/or deceptive (Was: Re: What's cooking in git.git (Jun 2021, #06; Thu, 17)) Felipe Contreras
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABPp-BG53Kd7MhzE3hdq5fjBQVV2Ew3skcUCAuTfM5daP2wmZA@mail.gmail.com \
    --to=newren@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).