Jonas Borgström

This check is in place to detect when a repository has been replaced with an older copy of itself. This happens naturally is situations like when the repository itself is...

That's strange. I have pretty much the same setup myself (cifs mounted synology nas) and it seems to work just fine. Is it always the same files that triggers these...

> What distro are you on and what mount options are you using? I'm using Arch Linux (Linux 3.15.7) and exactly the same mount options. Judging by the strace output...

How reproducible is it? Does it always happen on the same file/files? If so, I could write a minimal test program that uses the exact same syscalls and see if...

Hi guys, sorry for chiming in so late. I'm glad for all the attention and interest people are showing for Attic lately, and I know you've been keeping busy (30+...

> I can follow that you are a uncomfortable with people who you do not really know merging stuff (I would somehow feel same I guess). No, that's not really...

The end game for me has never been to keep this project as a one man shop where every single line of code is written by me. Just to make...

The reason for this behaviour is that the only thing we know about original mount point directory is the name. The data we get from stat() is from the mounted...

Right, I sort of expected that somebody would run into something like this. We could always extend this feature to a list of known locations. Could you explain a little...

I've never seen this before and it's not expected to ever happen. Is NFS, CIFS or some other kind of potentially unreliable filesystem used anywhere in this setup (on the...