From: Jonathan Nieder <jrnieder@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Michael Muré" <batolettre@gmail.com>,
git@vger.kernel.org, "Scott Chacon" <schacon@gmail.com>,
"Stefan Monnier" <monnier@iro.umontreal.ca>,
"Matthias Beyer" <mail@beyermatthias.de>,
"Julian Ganz" <neither@nut.email>
Subject: Re: git-bug: Distributed bug tracker embedded in git
Date: Sat, 18 Aug 2018 22:01:47 -0700 [thread overview]
Message-ID: <20180819050147.GA207351@aiede.svl.corp.google.com> (raw)
In-Reply-To: <87y3d3m2e4.fsf@kyleam.com>
(+ git-dit authors)
Kyle Meyer wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:
>> I believe you're thinking of TicGit[1].
>>
>> Some other related work is listed at [2]. Most of these projects have
>> gone quiet:
>>
>> - ditz[3]
>> - git-issues[4]
>> - cil[5]
>> - Bugs Everywhere[6]
>> - milli by Steve Kemp, which I haven't found a copy of
>> - simple defects[7]
>> - kipling[8]
>
> To add to that list: There's also BuGit [1,2], though it too seems to
> have gone quiet.
I just found a good list on a non Git-specific wiki[3] that is more
helpful (more up to date and has more discussion) than the list on the
Git wiki.
It might be a good place to coordinate and compare notes. git-dit[4]
in particular seems to have very similar goals and a similar data
model. In my ideal world there may be a path forward that involves
working more closely together.
Thanks,
Jonathan
> [1]: https://gitlab.com/monnier/bugit
> [2]: https://public-inbox.org/git/jwva8psr6vr.fsf-monnier+gmane.comp.version-control.git@gnu.org/
[3] https://dist-bugs.branchable.com/software/
[4] https://github.com/neithernut/git-dit
next prev parent reply other threads:[~2018-08-19 5:01 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
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 [this message]
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=20180819050147.GA207351@aiede.svl.corp.google.com \
--to=jrnieder@gmail.com \
--cc=batolettre@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kyle@kyleam.com \
--cc=mail@beyermatthias.de \
--cc=monnier@iro.umontreal.ca \
--cc=neither@nut.email \
--cc=schacon@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.
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).