Andreas Neuhaus

Hey @cberner. Thanks a lot for adding atime/mtime support! Though there are two reasons why I'd like to delay this PR a bit. 1) I'd like to finish #126 first...

I'm so sorry about the slow progress, I don't get a lot of free time these days to work on this. I just added the new filesystem trait and started...

I never worked with crossbeam before, but I see the advantage here. I generally like this changes, however I actually think that rust-fuse shouldn't deal with threads at all and...

Thanks for the report. I guess I didn't take care of big endian platform at all when writing the serialization. I'd like to revamp the kernel communication / serialization anyway,...

I recently improved operation request handling and added big endian tests. I'm planning to do something similar with reply handling. Do you happen to know how we could best cover...

@nabijaczleweli Nice, thanks for the hint. From what I see, it's basically using [cross](https://github.com/rust-embedded/cross). Unfortunately, fuse-sys depends on libfuse, so we also need libfuse for the target architecture by either...

You're right that the usage of the `log` crate should be documented better. The examples show how env_logger is initialized to get log output, but I agree that this can...

Back then when rust-fuse was created, we intentionally chose to have no public constructors to ensure that implementations comply with what the kernel protocol requires. Nowadays the interface on the...

As far as I remember, 7.8 was the most common version supported by all platforms back those days. I agree that this is ancient and that we should move on...

This sounds very interesting, I always wanted to have a future-like interface in rust-fuse that makes it easy to reply synchronously or asynchronously (that's why we came up with the...