git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Contributions which I feel are dangerous and/or deceptive (Was: Re: What's cooking in git.git (Jun 2021, #06; Thu, 17))

From
Elijah Newren <newren@gmail.com>
Date
Jun 17, 2021, 15:06 UTC
Message-ID
<CABPp-BE95Y0+d6yVQ0ZqRWnknqc3N1vL04VYoqy-7mvQckfuaQ@mail.gmail.com>
In-Reply-To
<60cb5a02f1b31_1259c2086f@natae.notmuch>

On Thu, Jun 17, 2021 at 7:19 AM Felipe Contreras <felipe.contreras@gmail.com> wrote:

Show 14 quoted lines
>
> 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'.
...
> Do you see anything wrong with these particular patches?
...
Sorry for responding when I said I wouldn't but let me clarify my own email.

The *code* changes in fc/pull-cleanups are good, I said as much previously. The commit messages are also fine, except for the misleading Reviewed-by claim that you still aren't addressing. That could be overlooked on its own.

Any other problematic patches or portions thereof of yours could easily have been written off as mistakes and been no big deal.

My concern is primarily in how you *respond* to feedback. I feel you have displayed a callous disregard for what others find critical and important, and appear to be unwilling or unable to adapt and work with the community. It was particularly your recent emails with Peff at [1], [2], and [3] that have me deeply troubled. Troubled enough that I do not want my name used to endorse your changes, particularly when I already pointed out that you have used my name in a false endorsement of your patch and you have now responded to but not corrected that problem (including again just now in this thread), making it appear to me that this was no mistake. I do not want such false endorsements to occur again, and felt I needed to speak up to make that happen.

[1] https://lore.kernel.org/git/60c647c1d9b5c_41f452089@natae.notmuch/ [2] https://lore.kernel.org/git/60c82a622ae66_e5292087f@natae.notmuch/ [3] https://lore.kernel.org/git/60c87fc6a87ba_e6332084f@natae.notmuch/

Previous: Felipe ContrerasNext: Felipe Contreras
Message 6 of 18 in “What's cooking in git.git (Jun 2021, #06; Thu, 17)”
  1. Junio C HamanoJun 17, 2021
  2. jh/builtin-fsmonitor, was Re: What's cooking in git.git (Jun 2021, #06; Thu, 17)Johannes Schindelin, Jun 17, 2021
  3. js/subtree-on-windows-fix, was Re: What's cooking in git.git (Jun 2021, #06; Thu, 17)Johannes Schindelin, Jun 17, 2021
  4. Contributions which I feel are dangerous and/or deceptive (Was: Re: What's cooking in git.git (Jun 2021, #06; Thu, 17))Elijah Newren, Jun 17, 2021
  5. Felipe ContrerasJun 17, 2021
  6. Elijah NewrenJun 17, 2021
  7. Felipe ContrerasJun 17, 2021
  8. Felipe ContrerasJun 17, 2021
  9. brian m. carlsonJun 17, 2021
  10. Jeff KingJun 18, 2021
  11. Felipe ContrerasJun 18, 2021
  12. Junio C HamanoJun 19, 2021
  13. Ignoring valid workFelipe Contreras, Jun 19, 2021
  14. Felipe ContrerasJun 18, 2021
  15. Jeff HostetlerJun 18, 2021
  16. Emily ShafferJun 25, 2021
  17. Randall S. BeckerJun 25, 2021
  18. Jeff HostetlerJun 28, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.