From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: linux-btrfs@vger.kernel.org
Subject: python-btrfs v7
Date: Sun, 28 May 2017 19:34:04 +0200 [thread overview]
Message-ID: <be800613-2bc3-14f3-707a-2ea34a6567a1@mendix.com> (raw)
I just tagged v7 of the python btrfs library:
https://github.com/knorrie/python-btrfs
This is a small release, with some fixes and a few new examples:
python-btrfs v7, May 28 2017
* Also unpack bitmaps when showing the free space tree
* Fixes:
- A few unfortunate typos in __str__ methods of objects
* Examples added:
- Show background subvolume removal progress.
- Show metadata tree sizes in bytes and amount of tree blocks.
- Show file info by tree and inode number
Have fun,
--
Hans van Kranenburg
reply other threads:[~2017-05-28 17:34 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=be800613-2bc3-14f3-707a-2ea34a6567a1@mendix.com \
--to=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).