From: Jakub Narebski <jnareb@gmail.com>
To: Thomas Harning <harningt@gmail.com>
Cc: <git@vger.kernel.org>
Subject: Re: Bug-tracking tools that handle branch/merge/etc
Date: Tue, 04 Mar 2008 14:24:21 -0800 (PST) [thread overview]
Message-ID: <m3ve42gmae.fsf@localhost.localdomain> (raw)
In-Reply-To: <20080304170903.7b029fc3@gmail.com>
Thomas Harning <harningt@gmail.com> writes:
> Partly referring back to the discussion last June
> (http://article.gmane.org/gmane.comp.version-control.git/49734)... has
> there been any developments in the area of a BTS that can grok GIT in a
> sane way?
Unless you count work-in-progress Grit (http://git.madism.org/?p=grit.git)
I think the answer is no. The 'after the fact commit annotation' aka
git-notes are also as far as I can see abandoned.
http://git.or.cz/gitwiki/InterfacesFrontendsAndTools#head-3a410db622d55b4dd88d91437d2c953f6b730542
> Main concept I see as important for a BTS grokking git:
> * Capability of following branches/merges in a way that
> you can see a list of bugs that affect a branch at any point
> in time.
>
> Niceties include:
> * The ability to 'distribute' this so bug tracking is as disconnected
> as coding itself (great for airplane-trip coding sessions)
> * Ability to watch incoming commits (suppose the BTS can 'pull' from
> various sources on occasion) for messages marking a bug as
> in-progress/fixed/re-opened/etc.
> * Local-application GUI integration... ex: gitk/git-gui + BT
BTW. you can put it in SoC2008Ideas as a project for Google Summer of
Code 2008... then try to find a mentor for this project ;-)
http://git.or.cz/gitwiki/SoC2008Ideas
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2008-03-04 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 22:09 Bug-tracking tools that handle branch/merge/etc Thomas Harning
2008-03-04 22:24 ` Jakub Narebski [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=m3ve42gmae.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=harningt@gmail.com \
/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).