From: Thomas Harning <harningt@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Matthieu Moy <Matthieu.Moy@imag.fr>,
Pierre Habouzit <madcoder@debian.org>, <git@vger.kernel.org>
Subject: Re: [RFC] Idea for Git Bugtracking Tool
Date: Mon, 10 Mar 2008 23:29:17 -0400 [thread overview]
Message-ID: <20080310232917.7c71ccbe@shiva> (raw)
In-Reply-To: <m3zltaf7vs.fsf@localhost.localdomain>
On Fri, 07 Mar 2008 15:10:18 -0800 (PST)
Jakub Narebski <jnareb@gmail.com> wrote:
> * Bugs Everywhere (http://bugseverywhere.org), written in Python,
> developed in Bazaar, has Git backend support. Formerly written by
> Panoramic Feedback (note that there is stale version of this tool),
> picked up by one of developers
This doesn't appear to let you mark bugs as existing at previous points
in history... which partly removes the usefulness of branch tracking....
Grit has the same problems it seems... (at least at the state it was
the last time I saw it).. besides the problem of being gone.
> * DisTract (http://www.distract.wellquite.org), written in Haskell,
> uses Monotone as backend. Has good reviews on blogs, e.g. by
> Masukomi.
Monotone+Haskell+Local Firefox... doesn't look like this will go far
in the real world where people w/o the entire actual would like to post
bugs...
>
> * DITrack (http://www.ditrack.org), written in Python, currently
> uses Subversion as backend, has plans to be backend-agnostic.
> Inspired by Subissue.
Doesn't seem to be able to deal w/ branches particularly... looks more
like a way to work as an offline-capable bug tracking system...
I've posted up a wiki @ http://www.eharning.us/wiki/stick/ for a
working concept for how a branch-tracking w/ possibility for
distribution... Feel free to comment on the page or (preferable) use
the Discussion page...
prev parent reply other threads:[~2008-03-11 3:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 19:22 [RFC] Idea for Git Bugtracking Tool Thomas Harning
2008-03-06 20:08 ` Matthieu Moy
2008-03-07 23:10 ` Jakub Narebski
2008-03-08 13:42 ` Pierre Habouzit
2008-03-08 14:23 ` Jakub Narebski
2008-03-08 15:02 ` Pierre Habouzit
2008-03-09 8:26 ` Jan Hudec
2008-03-11 3:29 ` Thomas Harning [this message]
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=20080310232917.7c71ccbe@shiva \
--to=harningt@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=madcoder@debian.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.
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 NNTP newsgroup(s).