From: Jeff King <peff@peff.net>
To: Fredrik Gustafsson <iveqy@iveqy.com>
Cc: git@vger.kernel.org
Subject: Re: [Opinions] Integrated tickets
Date: Thu, 6 Nov 2014 00:53:48 -0500 [thread overview]
Message-ID: <20141106055348.GC22835@peff.net> (raw)
In-Reply-To: <20141105124429.GF15384@paksenarrion.iveqy.com>
On Wed, Nov 05, 2014 at 01:44:29PM +0100, Fredrik Gustafsson wrote:
> So my question is:
>
> what's your opinions on building an integrated ticket system on top of git?
I think it's a nice concept, but there have been several
implementations, and AFAIK none of them is incredibly popular. I do not
know offhand if the problem is the concept or the implementations (I
looked at them long ago but don't remember enough to provide any sort of
reasonable critique).
I started to assemble a list of pointers, but I realized that 4 out of 5
of the projects that I had looked at a few years ago no longer exist. ;)
Here's an article from last year with a nice overview of the (non-)state
and links to other sources:
https://www.stationary-traveller.eu/distributed-bug-trackers.html
> and (maybe mostly for Junio)
>
> Would such system possible be included in git.git?
I am not Junio, but I would have to say: probably not. This seems like
something that can very easily sit on _top_ of git and use the git
plumbing. In the long-term git may want to grow features to make
integration more seamless, but we'd probably want to add them in a more
functionality-agnostic way (e.g., don't grow an option to attach bug
information to a commit; grow an option to attach arbitrary information
to a commit. We already have this part in the form of "git notes", but
there are likely other opportunities for integration).
-Peff
next prev parent reply other threads:[~2014-11-06 5:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 12:44 [Opinions] Integrated tickets Fredrik Gustafsson
2014-11-06 5:53 ` Jeff King [this message]
2014-11-06 18:45 ` Junio C Hamano
2014-11-11 12:46 ` Holger Hellmuth
2014-11-11 17:17 ` Junio C Hamano
2014-11-11 18:15 ` Holger Hellmuth
2014-11-11 18:24 ` Junio C Hamano
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=20141106055348.GC22835@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.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).