From: Jonathan Nieder <jrnieder@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Michael Muré" <batolettre@gmail.com>,
git@vger.kernel.org,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Subject: Re: git-bug: Distributed bug tracker embedded in git
Date: Sat, 18 Aug 2018 15:08:21 -0700 [thread overview]
Message-ID: <20180818220821.GC144170@aiede.svl.corp.google.com> (raw)
In-Reply-To: <8736vbqr2p.fsf@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason wrote:
> The reason I can drop a "git-whatever" in my $PATH and invoke it as "git
> whatever" is just a historical accident of how git was implemented.
No. This is a very deliberate design decision, to allow people to
prototype new Git commands (and to create the kind of ecosystem that
allows commands to be implemented outside Git.
[...]
> So we don't get to say "you never asked us about git-annex, we're using
> that name now" without considering how widely used it is. It's us who
> decided to expose the API of seamlessly integrating 3rd party tools.
I think we're talking past each other. I haven't proposed any blanket
policy. I'm saying that "git bug" is a bad name for this tool:
- it's hard to find with search engines
- it conflicts with some likely good future changes to Git
- it assumes that no one else will have some other refinement of the
Git bugtracker concept, that it is the only "git bug" tool
It's a namespace grab. There's nothing stopping someone from naming a
command "bug", either, but that doesn't make it a good idea. (I'm not
saying that was the intent --- that's just the effect.)
Meanwhile it looks like a neat tool, and I'm very supportive of the
idea. But you certainly still have not convinced me that the name is
a good idea, or that I shouldn't be bringing this up.
I'm not sure *what* you're trying to convince me of, actually.
Jonathan
next prev parent reply other threads:[~2018-08-18 22:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 22:06 git-bug: Distributed bug tracker embedded in git Michael Muré
2018-08-17 23:20 ` Tacitus Aedifex
2018-08-18 5:43 ` Jonathan Nieder
2018-08-18 12:24 ` Ævar Arnfjörð Bjarmason
2018-08-18 20:42 ` Jonathan Nieder
2018-08-18 21:53 ` Ævar Arnfjörð Bjarmason
2018-08-18 22:08 ` Jonathan Nieder [this message]
2018-08-18 22:19 ` Ævar Arnfjörð Bjarmason
2018-08-18 22:26 ` Jonathan Nieder
2018-08-19 21:08 ` Jeff King
2018-08-18 16:21 ` Junio C Hamano
2018-08-19 1:27 ` Jonathan Nieder
2018-08-19 4:00 ` Kyle Meyer
2018-08-19 5:01 ` Jonathan Nieder
2018-08-18 22:50 ` Jonathan Nieder
2018-08-19 0:45 ` Michael Muré
2018-08-19 1:14 ` Michael Muré
2018-08-19 2:06 ` Elijah Newren
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180818220821.GC144170@aiede.svl.corp.google.com \
--to=jrnieder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=batolettre@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).