From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Jeff King <peff@peff.net>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Siavash <siavash.askari.nasr@gmail.com>,
git@vger.kernel.org
Subject: Re: Renaming "non-contrib" things out of contrib/* (was "Re: [Bug] git-credential-netrc.perl[...]")
Date: Tue, 25 May 2021 15:51:34 +0900 [thread overview]
Message-ID: <xmqqtumrfgqx.fsf@gitster.g> (raw)
In-Reply-To: <87o8d0o2or.fsf@evledraar.gmail.com> (=?utf-8?B?IsOGdmFyIEFy?= =?utf-8?B?bmZqw7Zyw7A=?= Bjarmason"'s message of "Mon, 24 May 2021 12:05:34 +0200")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> I wonder if just a top-level completion/* wouldn't be best, or if we
> want to group them all together something like
> optional/{completion,credential}/ or other name suggesting that these
> are meant to interact with not-always-present 3rd party software. Maybe
> integrations/* ?
Add-ons?
I think dispelling the conception by distro people must begin with
an update to contrib/README where it clearly says these are
"contributed software" that are not part of "Git". They are not
something we stand behind like what we have in the rest of the
source tree.
Also, the description there is rather stale. For example, the last
paragraph must go as its entirety. The ecosystem has expanded
thousand-fold since the document was written, and we no longer
encourage people to add new things to contrib/ directory at all. We
instead encourage them to write and sell their ware on their own
merit alone, without planning to "borrow" authority and gain undue
advantage over its competitors by being in the contrib/ area in our
tree.
.
next prev parent reply other threads:[~2021-05-25 6:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 9:51 [Bug] git-credential-netrc.perl is not built and is not available in `exec-path` Siavash
2021-05-20 20:41 ` Jonathan Nieder
2021-05-21 10:26 ` Siavash
2021-05-21 1:55 ` brian m. carlson
2021-05-21 10:04 ` Jeff King
2021-05-21 22:27 ` brian m. carlson
2021-05-23 19:57 ` Jeff King
2021-05-24 3:01 ` Felipe Contreras
2021-05-24 10:05 ` Renaming "non-contrib" things out of contrib/* (was "Re: [Bug] git-credential-netrc.perl[...]") Ævar Arnfjörð Bjarmason
2021-05-24 17:21 ` Felipe Contreras
2021-05-24 23:18 ` Ævar Arnfjörð Bjarmason
2021-05-25 1:23 ` Felipe Contreras
2021-05-25 6:51 ` Junio C Hamano [this message]
2021-05-25 7:31 ` Bagas Sanjaya
2021-05-25 9:05 ` Felipe Contreras
2021-05-25 10:35 ` Felipe Contreras
2021-05-21 10:06 ` [Bug] git-credential-netrc.perl is not built and is not available in `exec-path` Jeff King
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=xmqqtumrfgqx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=siavash.askari.nasr@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).