unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Aaron Conole <aconole@bytheb.org>
Cc: emacs-devel@gnu.org
Subject: Re: BuGit
Date: Tue, 02 Feb 2016 14:40:33 -0500	[thread overview]
Message-ID: <jwvfuxakiko.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20160202183713.GA28586@bytheb.org> (Aaron Conole's message of "Tue, 2 Feb 2016 21:37:13 +0300")

>> 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).
> This looks great! Is there an intent to integrate this as another set of
> "git branch metadata" on existing repositories? IE: can I take a repo like
> emacs, and just use bugit on top of it? Is that ever intended as a workflow?

You can indeed store the bug database in the same repository as the
project's source code.  Not in the same branch, OTOH.


        Stefan



  reply	other threads:[~2016-02-02 19:40 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   ` Stefan Monnier [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvfuxakiko.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=aconole@bytheb.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).