public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Florian Mickler <florian@mickler.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Re-enable rc6 w/fix
Date: Tue, 15 Mar 2011 22:32:09 +0100	[thread overview]
Message-ID: <20110315223209.52cc27cc@schatten.dmk.lab> (raw)
In-Reply-To: <1bdc18$jsdqub@fmsmga002.fm.intel.com>

On Tue, 15 Mar 2011 07:59:48 +0000
Chris Wilson <chris@chris-wilson.co.uk> wrote:

> > Resolve https://bugzilla.kernel.org/show_bug.cgi?id=28582
> 
> I understood the convention (to aide those running external scripts) was
> either Bugzilla: or References:

Thx for considering those poor souls that try to follow up on all
those loose ends.... But here it actually doesn't matter all that much,
the 'https://bugzilla.kernel.org/show_bug.cgi?id=' - prefix to the
bug number is enough of a give-away to parse the changelog for. 

Still, I expect there are people who like consistency and so, from my
experience of changelog digging you are indeed correct, that
References: or Bugzilla: seems to be prevalent.

Regards,
Flo

  parent reply	other threads:[~2011-03-15 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15  4:55 [PATCH] drm/i915: Re-enable rc6 w/fix Ben Widawsky
2011-03-15  5:00 ` Ben Widawsky
2011-03-15  7:12   ` Ben Widawsky
2011-03-15  9:58     ` Chris Wilson
2011-03-15  7:59 ` Chris Wilson
2011-03-15 17:15   ` Daniel Vetter
2011-03-15 21:32   ` Florian Mickler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-15  4:52 Ben Widawsky

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=20110315223209.52cc27cc@schatten.dmk.lab \
    --to=florian@mickler.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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