All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Florian Mickler <florian@mickler.org>, dri-devel@lists.freedesktop.org
Subject: Re: commit notifications in bugzilla
Date: Thu, 30 Jun 2011 11:48:45 +0100	[thread overview]
Message-ID: <1309430924_45071@CP5-2952> (raw)
In-Reply-To: <20110630123805.07c163bc@schatten.dmk.lab>

On Thu, 30 Jun 2011 12:38:05 +0200, Florian Mickler <florian@mickler.org> wrote:
> Hi, 
> I have just posted notifications to the bugs.fdo bugzilla for commits
> out of v2.6.39..v3.0-rc5 that mention a bug via full link at
> bugs.fdo . 
> 
> See for example https://bugs.freedesktop.org/show_bug.cgi?id=38529 .
> 
> Is this considered signal or noise? 

I find it useful. My policy has been not to close bugs until the patch has
been applied to an upstream tree. So confirmation that it did arrive, and
its identifier in Linus' tree, is indeed valuable.

Thanks,
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

      reply	other threads:[~2011-06-30 10:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30 10:38 commit notifications in bugzilla Florian Mickler
2011-06-30 10:48 ` Chris Wilson [this message]

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=1309430924_45071@CP5-2952 \
    --to=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=florian@mickler.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.