From: Holger Hellmuth <hellmuth@ira.uka.de>
To: Junio C Hamano <gitster@pobox.com>, Fredrik Gustafsson <iveqy@iveqy.com>
Cc: git@vger.kernel.org
Subject: Re: [Opinions] Integrated tickets
Date: Tue, 11 Nov 2014 13:46:26 +0100 [thread overview]
Message-ID: <54620522.4060600@ira.uka.de> (raw)
In-Reply-To: <xmqqvbmsgocj.fsf@gitster.dls.corp.google.com>
Am 06.11.2014 um 19:45 schrieb Junio C Hamano:
> 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?
I would expect a ticket to be annotating the commit or version tag where
the bug was found, which usually isn't the commit where the bug was
introduced.
next prev parent reply other threads:[~2014-11-11 13:02 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
2014-11-11 12:46 ` Holger Hellmuth [this message]
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=54620522.4060600@ira.uka.de \
--to=hellmuth@ira.uka.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).