From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2021, #06; Thu, 17)
Date: Sat, 19 Jun 2021 16:18:23 +0900 [thread overview]
Message-ID: <xmqqmtrmjpa8.fsf@gitster.g> (raw)
In-Reply-To: <YMvofq5aSryQzpZQ@coredump.intra.peff.net> (Jeff King's message of "Thu, 17 Jun 2021 20:27:42 -0400")
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. Also, if some contributors get too annoying
to be worth our time interacting with, it is OK to ignore them.
> I don't think this topic is particularly urgent, so I'm OK to drop it
> for now (and as always, it's your choice what you work on). But I'm
> worried about the general precedent / principle.
next prev parent reply other threads:[~2021-06-19 7:18 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 [this message]
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=xmqqmtrmjpa8.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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).