On Wed, Nov 12, 2014 at 10:16 PM, <to...@acm.org> wrote: > When opening a repo, if you select to overwrite all files, and a file > to be updated happens to be read-only (R attrib set), the overwrite fails > (it should) but if you then change the read-only to read-write, and try to > see changes or try to revert the failed to update file with the repo > version, nothing happens. FOSSIL somehow assumes that the checkout is in a > correct state, even though it failed to overwrite, and the repo and > check-out have different copies of the same file. >
That's apparently a bug (and thank you for the reproduction steps), but i've gotta ask: why on earth would have a read-only file under fossil's control (as opposed to having read-only generated files, which i do to keep me from accidentally editing the generated Makefiles instead of their input tempates)? Fossil doesn't store/set any attributes except +x (git doesn't support other attributes either (anymore), based on what i've read). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
