mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Felipe Contreras <>
To: "Junio C Hamano" <>,
	"Ævar Arnfjörð Bjarmason" <>
Cc: Felipe Contreras <>,
	Jeff King <>,
	"brian m. carlson" <>,
	Siavash <>,
Subject: Re: Renaming "non-contrib" things out of contrib/* (was "Re: [Bug] git-credential-netrc.perl[...]")
Date: Tue, 25 May 2021 05:35:35 -0500	[thread overview]
Message-ID: <60acd2f76e290_2257a208e9@natae.notmuch> (raw)
In-Reply-To: <xmqqtumrfgqx.fsf@gitster.g>

Junio C Hamano wrote:
> Ævar Arnfjörð Bjarmason <> 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?

An add-on extends the functionality of the core. These are not 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.

They know what the README says.

But they also know what the README says is not true. git-completion.bash
is completely fine for wide-spread use, and in fact, it's already used
widely. They are not going to remove
`/usr/share/bash-completion/completions/git` just because upstream
developers write something innacurate in contrib/README.

Their first responsibility is to provide the most usable system they can
to their users. git completions for bash is essential towards that goal.

As long as the README contains innacurate information they will be
forced to ignore it, and keep installing valuable stuff from contrib/ at
their own discretion.

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

They why did you reject my git-related tool[1], and yet accepted a
direct competitor git-contacts[2]? It certainly looks like you have
undue advantage to one tool over the other.

There's is also hg-to-git, a competition of git-remote-hg.

And for that matter git-completion.zsh, a tool I created, and is now in
competition with git-completion[3].

It would be nice if what was stated above was true, but alas it's not.



Felipe Contreras

  parent reply	other threads:[~2021-05-25 10:37 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
2021-05-25  7:31               ` Bagas Sanjaya
2021-05-25  9:05                 ` Felipe Contreras
2021-05-25 10:35               ` Felipe Contreras [this message]
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:

  List information:

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

  git send-email \
    --in-reply-to=60acd2f76e290_2257a208e9@natae.notmuch \ \ \ \ \ \ \ \

* 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

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