git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Bug-tracking tools that handle branch/merge/etc

From
Thomas Harning <harningt@gmail.com>
Date
Mar 4, 2008, 22:09 UTC
Message-ID
<20080304170903.7b029fc3@gmail.com>

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
Next: Jakub Narebski
Message 1 of 2 in “Bug-tracking tools that handle branch/merge/etc”
  1. Thomas HarningMar 4, 2008
  2. Jakub NarebskiMar 4, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.