From: "Aurélien Aptel" <aurelien.aptel+emacs@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: BuGit
Date: Tue, 2 Feb 2016 17:10:08 +0100 [thread overview]
Message-ID: <CA+5B0FNy_22YBGd+Akq8zmd+3-hvJJq9q2RdxqQkCVR19VZV2A@mail.gmail.com> (raw)
In-Reply-To: <jwvh9hrkvab.fsf-monnier+emacs@gnu.org>
On Tue, Feb 2, 2016 at 4:09 PM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> For those curious about what I've been upto lately, one of the things
> I've been working on is a new distributed issue tracking system which
> I call BuGit:
>
> https://gitlab.com/monnier/bugit
>
> It's still primitive (only the command-line UI and the email
> notification system are more or less complete: the web UI is still
> read-only, and there is no email UI at all).
I like the offline work+sync later feature. This looks really
interesting. I see in the source you have code to import debbugs
issues. Do you have an emacs-bugit repo?
How does querying for say open bugs work? Do you think it can scale to
emacs bugs database?
The web and especially the email UI are going to be a PITA to write
but they are essential so keep up the good work!
next prev parent reply other threads:[~2016-02-02 16:10 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 ` Aurélien Aptel [this message]
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 ` BuGit Stefan Monnier
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=CA+5B0FNy_22YBGd+Akq8zmd+3-hvJJq9q2RdxqQkCVR19VZV2A@mail.gmail.com \
--to=aurelien.aptel+emacs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.