From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Subject: Ignoring valid work
Date: Sat, 19 Jun 2021 12:27:12 -0500 [thread overview]
Message-ID: <60ce28f025b09_cc2b120896@natae.notmuch> (raw)
In-Reply-To: <xmqqmtrmjpa8.fsf@gitster.g>
Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > Hmm. I'm not sure if that's a good resolution here. I do think many
> > people were positive in moving in that direction. If there's a
> > contributor that people have trouble working with, I'm OK giving up on
> > possible contributions they could make, even adaptations of their work.
> >
> > But if by working in an area they poison it for others (because there's
> > no desire to work with them, but no desire to step on their toes) that
> > doesn't seem like a workable long-term strategy.
>
> You may lick a corner of a piece of cake and think that it would
> repel other people enough to leave only you to consider eating it,
> but no, in this project, you aren't allowed to lick a Makefile and
> claim that you own it.
I wonder who might have attempted to do that in your view.
In reality have I have never attempted to do anything remotely close to
that.
> Also, if some contributors get too annoying to be worth our time
> interacting with, it is OK to ignore them.
But do you have a valid reason? Or is it just petty personal animus?
Talk is cheap. Code is what speaks.
I'm doing valid, useful, and substantial code.
It is the project that suffers from ignoring it.
Ignore me all you want, but the code doesn't stop being valid.
https://lore.kernel.org/git/20210618203057.790320-1-felipe.contreras@gmail.com
https://lore.kernel.org/git/20210618215231.796592-1-felipe.contreras@gmail.com
--
Felipe Contreras
next prev parent reply other threads:[~2021-06-19 17:27 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
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 ` Felipe Contreras [this message]
2021-06-18 4:20 ` 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=60ce28f025b09_cc2b120896@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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).