From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Timofey Titovets <nefelim4ag@gmail.com>
Cc: Tim Walberg <twalberg@comcast.net>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs Heatmap - v4 ... colors!!
Date: Fri, 3 Feb 2017 15:27:12 +0100 [thread overview]
Message-ID: <160ddbc9-fb38-56e6-cffe-650f9eb5c535@mendix.com> (raw)
In-Reply-To: <CAGqmi76pqhK1kx5mOH8=D2z90beZhkmPWj=4kLxO7aQD_jbHsw@mail.gmail.com>
On 02/03/2017 03:18 PM, Timofey Titovets wrote:
> 2017-02-03 15:57 GMT+03:00 Hans van Kranenburg <hans.van.kranenburg@mendix.com>:
>> On 02/03/2017 12:25 PM, Timofey Titovets wrote:
>>> Thank you for your great work:
>>> JFYI Packaged in AUR:
>>> https://aur.archlinux.org/packages/python-btrfs-heatmap/
>>
>> Hey, thanks.
>>
>> Just wondering... what is that btrfs.py you refer to in...
>> https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=python-btrfs ?
>>
>> It's a package, not a single file, so maybe that compile command doesn't
>> do anything? I'm not familiar with arch, so correct me if I'm wrong.
>>
>> .
>> ├── btrfs
>> │ ├── crc32c.py
>> │ ├── ctree.py
>> │ ├── __init__.py
>> │ ├── ioctl.py
>> │ ├── utils.py
>>
>
> You right, compile command are useless, so i did remove it, thanks.
-$ python2 -m compileall btrfs
Listing btrfs ...
Compiling btrfs/__init__.py ...
Compiling btrfs/crc32c.py ...
Compiling btrfs/ctree.py ...
Compiling btrfs/ioctl.py ...
Compiling btrfs/utils.py ...
.
├── btrfs
│ ├── crc32c.py
│ ├── crc32c.pyc
│ ├── ctree.py
│ ├── ctree.pyc
│ ├── __init__.py
│ ├── __init__.pyc
│ ├── ioctl.py
│ ├── ioctl.pyc
│ ├── utils.py
│ └── utils.pyc
-$ python3 -m compileall btrfs
Listing 'btrfs'...
Compiling 'btrfs/__init__.py'...
Compiling 'btrfs/crc32c.py'...
Compiling 'btrfs/ctree.py'...
Compiling 'btrfs/ioctl.py'...
Compiling 'btrfs/utils.py'...
.
├── btrfs
│ ├── crc32c.py
│ ├── ctree.py
│ ├── __init__.py
│ ├── ioctl.py
│ ├── __pycache__
│ │ ├── crc32c.cpython-35.pyc
│ │ ├── ctree.cpython-35.pyc
│ │ ├── __init__.cpython-35.pyc
│ │ ├── ioctl.cpython-35.pyc
│ │ └── utils.cpython-35.pyc
│ └── utils.py
--
Hans van Kranenburg
next prev parent reply other threads:[~2017-02-03 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 19:53 Btrfs Heatmap - v4 ... colors!! Hans van Kranenburg
[not found] ` <20170118003838.GA4136@comcast.net>
2017-01-19 0:08 ` Hans van Kranenburg
2017-02-03 11:25 ` Timofey Titovets
2017-02-03 12:57 ` Hans van Kranenburg
2017-02-03 14:18 ` Timofey Titovets
2017-02-03 14:27 ` Hans van Kranenburg [this message]
2017-02-03 14:36 ` Timofey Titovets
2017-02-03 14:46 ` 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=160ddbc9-fb38-56e6-cffe-650f9eb5c535@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nefelim4ag@gmail.com \
--cc=twalberg@comcast.net \
/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).