All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Harning <harningt@gmail.com>
To: <git@vger.kernel.org>
Subject: Bug-tracking tools that handle branch/merge/etc
Date: Tue, 4 Mar 2008 17:09:03 -0500	[thread overview]
Message-ID: <20080304170903.7b029fc3@gmail.com> (raw)

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?

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

             reply	other threads:[~2008-03-04 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04 22:09 Thomas Harning [this message]
2008-03-04 22:24 ` Bug-tracking tools that handle branch/merge/etc Jakub Narebski

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=20080304170903.7b029fc3@gmail.com \
    --to=harningt@gmail.com \
    --cc=git@vger.kernel.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 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.