From: Junio C Hamano <gitster@pobox.com>
To: Fredrik Gustafsson <iveqy@iveqy.com>
Cc: git@vger.kernel.org
Subject: Re: [Opinions] Integrated tickets
Date: Thu, 06 Nov 2014 10:45:16 -0800 [thread overview]
Message-ID: <xmqqvbmsgocj.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20141105124429.GF15384@paksenarrion.iveqy.com> (Fredrik Gustafsson's message of "Wed, 5 Nov 2014 13:44:29 +0100")
Fredrik Gustafsson <iveqy@iveqy.com> writes:
> 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?
Integrated? Not really, unless we already have a clear winner in
the marketplace that we can just ship in contrib/ or something, and
even then, the Git ecosystem is now rich enough and the userbase
strong enough that having something in contrib/ adds much less value
than additional burden of having to keep up with the upstream, and
user confusion coming from possible version skew from the upstream.
It used to make a lot of sense to ship Git with things like gitweb
and gitk when we were trying to gain momentum, but it is no longer
2005 ;-). Even kernel.org does not run gitweb anymore.
This is a tangent, but I personally do not think "ticket" meshes
very well with "commit". If you already know which commit was
problematic, why are you annotating it with a ticket before
reverting it first?
next prev parent reply other threads:[~2014-11-06 18:45 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
2014-11-06 18:45 ` Junio C Hamano [this message]
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=xmqqvbmsgocj.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--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).