Miquel van Smoorenburg

I made a demo account on nextcloud.com, and did a webdav PROPFIND request: ``` $ curl -i --user "admin:admin" -X OPTIONS https://demo.nextcloud.com/ae8oobah/remote.php/dav/files/admin/ HTTP/1.1 200 OK Date: Tue, 19 Mar 2019...

Well, yes, that *is* the SabreDav standard, to use `PATCH`. In a specific way, see [http://sabre.io/dav/http-patch/](http://sabre.io/dav/http-patch/). However, if a server implements this, it _must_ indicate that by putting `sabredav-partialupdate` in...

If there is no followup to this issue I will close it tomorrow.

Let's keep this issue open since the Nextcloud issue is also still open.

I've added a go.mod file with a dependency on an older fuse package, now it builds again. That's a temporary fix. I'll work on a proper one.

Yes, you're right- it would involve adding `setgroups` code (actually, libc::SYS_setgroups) code in `suid.rs`. I'm looking at that right now.

The latest version in the repo now has support for this. You need to set the `supplementary-groups` option in the `unix` section to enable it: ``` [unix] supplementary-groups = true...

That's interesting, I was under the (apparently incorrect) impression that adding windows support would be hard. I recently made 'quota' and 'pam' features, I can see from your patches that...

Looks like that is a `RefCell` error. But there's only one place in the code where a `RefCell` is used, and that's in a thread_local section. Hmm. It could be...

Basically that trait (and the other ones in `fs`) mirror the functions from `std::fs` in the Rust standard library. `PUT` is open + write, so you need to implement `DavFileSystem::open`....