From: Nikolay Borisov <nborisov@suse.com>
To: Hans van Kranenburg <hans.van.kranenburg@mendix.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: python-btrfs v10 preview... detailed usage reporting and a tutorial
Date: Mon, 24 Sep 2018 11:08:31 +0300 [thread overview]
Message-ID: <f50f64a5-eec5-da34-d07b-0a76d108f044@suse.com> (raw)
In-Reply-To: <db9f3d50-a1c7-8a27-c77c-393a1d89b421@mendix.com>
On 24.09.2018 00:54, Hans van Kranenburg wrote:
<snip>
.
>
> The bugs are all related to repeated kernel code all over the place
> containing a lot of if statements dealing with different kind of
> allocation profiles and their exceptions. What I ended up doing is
> making a few helper functions instead, see the commit "Add volumes.py,
> handling device / chunk logic". It would probably be nice to do the same
> in the kernel code, which would also solve the mentioned bugs and
> prevent new similar ones from happening.
Would you care to report each bug separately so they can be triaged and
fixed?
>
> Have fun,
>
next prev parent reply other threads:[~2018-09-24 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 21:54 python-btrfs v10 preview... detailed usage reporting and a tutorial Hans van Kranenburg
2018-09-23 23:19 ` Adam Borowski
2018-10-08 0:03 ` Hans van Kranenburg
2018-10-08 5:42 ` Adam Borowski
2018-09-24 8:08 ` Nikolay Borisov [this message]
2018-09-28 23:04 ` Hans van Kranenburg
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=f50f64a5-eec5-da34-d07b-0a76d108f044@suse.com \
--to=nborisov@suse.com \
--cc=hans.van.kranenburg@mendix.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).