From: Josef Bacik <jbacik@fusionio.com>
To: <linux-btrfs@vger.kernel.org>
Subject: Moving to bugzilla.kernel.org
Date: Tue, 30 Apr 2013 11:58:12 -0400 [thread overview]
Message-ID: <20130430155812.GE2580@localhost.localdomain> (raw)
Hello,
In an effort to be better about helping users with their bugs I've gotten
control over the btrfs component of bugzilla.kernel.org. I'm currently going
through all the bugs in this list and closing out the old ones (which is most of
them). From now on I'd like us to push users who report bugs onto
bugzilla.kernel.org so we can be sure we're keeping track of all the reported
issues and we can be more responsive to them, instead of what currently happens
where a few get a lot of personal attention and the rest get ignored because
we're already giving somebody attention when somebody else submits a bug report.
Let me know if you have any questions, thanks,
Josef
reply other threads:[~2013-04-30 15:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130430155812.GE2580@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox