From: Fredrik Gustafsson <iveqy@iveqy.com>
To: git@vger.kernel.org
Subject: [Opinions] Integrated tickets
Date: Wed, 5 Nov 2014 13:44:29 +0100 [thread overview]
Message-ID: <20141105124429.GF15384@paksenarrion.iveqy.com> (raw)
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 reply other threads:[~2014-11-05 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 12:44 Fredrik Gustafsson [this message]
2014-11-06 5:53 ` [Opinions] Integrated tickets Jeff King
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=20141105124429.GF15384@paksenarrion.iveqy.com \
--to=iveqy@iveqy.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 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).