git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: "Michael Muré" <batolettre@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-bug: Distributed bug tracker embedded in git
Date: Fri, 17 Aug 2018 22:43:00 -0700	[thread overview]
Message-ID: <20180818054300.GB241538@aiede.svl.corp.google.com> (raw)
In-Reply-To: <CACSZ0Pwzs2e7E5RUEPDcEUsa=inzCyBAptU7YaCUw+5=MutSsA@mail.gmail.com>

Hi,

Michael Muré wrote:

> I released today git-bug, a distributed bug tracker that embeds in
> git. It use git's internal storage to store bugs information in a way
> that can be merged without conflict. You can push/pull to the normal
> git remote you are already using to interact with other people. Normal
> code and bugs are completely separated and no files are added in the
> regular branches.

I am a bit unhappy about the namespace grab.  Not for trademark
reasons: the Git trademark rules are pretty clear about this kind of
usage being okay.  Instead, the unhappiness comes because a future Git
command like "git bug" to produce a bug report with appropriate
diagnostics for a bug in Git seems like a likely and useful thing to
get added to Git some day.  And now the name's taken.

Is it too late to ask if it's possible to come up with a less generic
name?

Separately from that, I'm happy to see progress being made in the
distributed bug tracker world; thanks for that!

Thanks,
Jonathan

  parent reply	other threads:[~2018-08-18  5:43 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 [this message]
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
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=20180818054300.GB241538@aiede.svl.corp.google.com \
    --to=jrnieder@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).