git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Tacitus Aedifex <aedifex@SDF.ORG>
To: git@vger.kernel.org
Cc: batolettre@gmail.com
Subject: Re: git-bug: Distributed bug tracker embedded in git
Date: Fri, 17 Aug 2018 23:20:24 +0000	[thread overview]
Message-ID: <20180817232024.GA25871@SDF.ORG> (raw)
In-Reply-To: <CACSZ0Pwzs2e7E5RUEPDcEUsa=inzCyBAptU7YaCUw+5=MutSsA@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit; format=flowed, Size: 366 bytes --]

I really like this idea. I've often wanted an integrated bug database like 
this. My solution has always been to have a subrepo storing bug reports and 
coments in .txt files and then using bash porcelain scripts to make a git-like 
interface. I think I like this better. My only nit is Go. That makes me sad.  
Someone should re-implement this in C or Rust.

//tæ

  reply	other threads:[~2018-08-17 23:20 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 [this message]
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
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=20180817232024.GA25871@SDF.ORG \
    --to=aedifex@sdf.org \
    --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).