All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Florian Mickler <florian@mickler.org>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: A patch referencing this bug report has been merged...
Date: Wed, 30 Jan 2013 11:14:01 +0200	[thread overview]
Message-ID: <87zjzrdodi.fsf@intel.com> (raw)


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

             reply	other threads:[~2013-01-30  9:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30  9:14 Jani Nikula [this message]
2013-03-02 18:35 ` A patch referencing this bug report has been merged Florian Mickler
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=87zjzrdodi.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=florian@mickler.org \
    --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.