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

[Opinions] Integrated tickets

From
Fredrik Gustafsson <iveqy@iveqy.com>
Date
Nov 5, 2014, 12:44 UTC
Message-ID
<20141105124429.GF15384@paksenarrion.iveqy.com>

Hi, many developers rely on ticket systems (githubs issues, trac, bugzilla, etc.). To me a ticket often has a relation to one or more commits.

Hence, even if git is functional in an offline enviroment, I can't work fully since none of the ticket systems above is distributed.

This can be solved with a distributed ticket system. Fossil SCM is one example of an integrated ticket system into a scm (although please don't think about this is something that must be web-based).

So my question is:
what's your opinions on building an integrated ticket system on top of git?
and (maybe mostly for Junio)
Would such system possible be included in git.git?

TL;DR; Is an integrated ticket system something for git?

-- 
Med vänlig hälsning
Fredrik Gustafsson

tel: 0733-608274
e-post: iveqy@iveqy.com
Next: Jeff King
Message 1 of 7 in “[Opinions] Integrated tickets”
  1. Fredrik GustafssonNov 5, 2014
  2. Jeff KingNov 6, 2014
  3. Junio C HamanoNov 6, 2014
  4. Holger HellmuthNov 11, 2014
  5. Junio C HamanoNov 11, 2014
  6. Holger HellmuthNov 11, 2014
  7. Junio C HamanoNov 11, 2014

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.