linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: nick <yocto6@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Bug on Kernel Bugzilla I Found Today
Date: Sat, 20 Sep 2014 22:35:31 -0400	[thread overview]
Message-ID: <541E3973.5080703@gmail.com> (raw)

Greeting to the Btrfs Developers and Community,
Today , I found a new bug on the kernel bugzilla related to btrfs and am wondering if this bug has been fixed yet.
Further due to my limited knowledge of the  btrfs code base, I lack the knowledge to fix bugs like this yet.In addition, 
due to this I will paste below this  message a link to the reported bug page on the kernel bugzilla . It would be very 
helpful for mycontinued  learning about the btrfs file system  if someone can CC me into the patches and/or discussion of 
this  bug in order to help me learn more about btrfs  and bugs related to btrfs, this  would be greatly appreciated and extremely
helpful for my learning. Hopefully eventually I can help fix bugs like this too and aid eventually in future btrfs development.
Cheers and Thanks for the Help with Xfs Tests,
Nick  
Link to the Bug:
https://bugzilla.kernel.org/show_bug.cgi?id=84631

                 reply	other threads:[~2014-09-21  2:35 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=541E3973.5080703@gmail.com \
    --to=yocto6@gmail.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;
as well as URLs for NNTP newsgroup(s).