From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Aurélien Aptel" <aurelien.aptel+emacs@gmail.com>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: BuGit
Date: Wed, 03 Feb 2016 08:04:52 -0500 [thread overview]
Message-ID: <jwvzivihs6a.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CA+5B0FPJP3DQUVh1TwaWxYj_n8Lsh+wO3K4w4ZUpCim-0fFLDA@mail.gmail.com> ("Aurélien Aptel"'s message of "Wed, 3 Feb 2016 11:21:47 +0100")
> I have found other similar projects (git based issue management) which
> you might be interested in:
> https://github.com/dspinellis/gi
> The README also links to similar projects:
Indeed, there are other distributed issue tracking systems out there
(the most mature being maybe Bugs Everywhere, IIRC).
What distinguishes BuGit is that it uses a representation that lets Git
take care of all the merging that can be done automatically (and there
are only very few cases where conflicts can arise, the only important
one so far is when the bug's name is changed concurrently), and that
individual issues can have their own life rather than being tied to
a particular database (so in an ideal world, when Debian gets an Emacs
bug and forwards it to us, we could share the same BuGit issue for it
(not the same issue Number, but same issue ID) so any comment added from
the Debian side appears in Emacs's database and vice versa).
Stefan
next prev parent reply other threads:[~2016-02-03 13:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 15:09 BuGit Stefan Monnier
2016-02-02 16:10 ` BuGit Aurélien Aptel
2016-02-02 16:43 ` BuGit Stefan Monnier
2016-02-03 10:37 ` BuGit Aurélien Aptel
2016-02-03 13:03 ` BuGit Stefan Monnier
2016-02-02 16:26 ` BuGit Nicolas Petton
2016-02-02 17:08 ` BuGit Stefan Monnier
2016-02-02 18:37 ` BuGit Aaron Conole
2016-02-02 19:40 ` BuGit Stefan Monnier
2016-02-02 19:30 ` BuGit Dmitry Gutov
2016-02-02 22:06 ` BuGit Stefan Monnier
2016-02-03 10:21 ` BuGit Aurélien Aptel
2016-02-03 13:04 ` Stefan Monnier [this message]
2016-02-03 16:45 ` BuGit John Wiegley
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvzivihs6a.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=aurelien.aptel+emacs@gmail.com \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.