From: Florian Mickler <fmickler@gmx.de>
To: Jani Nikula <jani.nikula@intel.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: A patch referencing this bug report has been merged...
Date: Sat, 2 Mar 2013 19:35:45 +0100 [thread overview]
Message-ID: <20130302193545.44b68282@schatten.dmk.lab> (raw)
In-Reply-To: <87zjzrdodi.fsf@intel.com>
On Wed, 30 Jan 2013 11:14:01 +0200
Jani Nikula <jani.nikula@intel.com> wrote:
>
> Hi Florian, all -
>
> First, thanks for your work on adding the bugzilla comments when patches
> referencing bugs get merged. I find it useful.
>
> Recently however there was a comment about a commit referencing a commit
> referencing the bug report. Turns out the comment was missing one level
> of indirection, it was really about a commit referencing a commit
> referencing a commit referencing the bug [1].
>
> Do we really need go that far, or is that a bug in your scripts? I think
> three levels of indirection is more noise than signal; two might be
> still be okay. What do others think?
>
> BR,
> Jani.
>
>
> [1] https://bugs.freedesktop.org/show_bug.cgi?id=52424#c56
Is it really a problem? I can change it of course, but I doubt it is
worth the hassle. At the moment I just record sha1 -> bug associations
and if in a commit message, the mentioned (full!) sha1 is associated to
a bug, I associate that commit with that bug.
If someone goes to the trouble to actually mention the sha1 in a
commit message, that probably means it really is an important
connection.
And if that commit is associated with a bug, then that should mean
something too.
Think about multiple attempts to fix a bug which get always reverted
because the hardware is really acting up in different ways with every
attempt...
As it is, I don't think it is worth the trouble. If you feel strongly
about the message, I can reword it to be somewhat unspecific about the
level of indirection... what do you think?
Regards,
Flo
p.s.: sorry for the late response, I'm having a bit of trouble with my
mail setup at the moment and too much to do...
next prev parent reply other threads:[~2013-03-02 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 9:14 A patch referencing this bug report has been merged Jani Nikula
2013-03-02 18:35 ` Florian Mickler [this message]
2013-03-03 17:05 ` Daniel Vetter
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=20130302193545.44b68282@schatten.dmk.lab \
--to=fmickler@gmx.de \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.