On Mar 3, 2015, at 4:00 PM, Ron W <[email protected]> wrote: > > And neither "fossil changes" nor "fossil ci" did not warn me about that.
Yeah, it’s a bit broken. If file attributes are considered a part of the file’s data, and not just local metadata, then: chmod +x foo f ci foo should result in a checkin even if foo hasn’t otherwise changed. Yes, I know about --allow-empty. The point is that metadata is being silently included along with data in a non-empty change, but a metadata change isn’t enough to trigger a checkin when the associated data hasn't also changed. I think I prefer the Subversion solution to this problem: svn propset svn:executable foo It’s wordy, but at least it makes explicit your wish to change the file’s metadata. Also, an svn property change can be checked in without an equivalent of --allow-empty. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
