On Tue, Mar 3, 2015 at 6:11 PM, Warren Young <[email protected]> wrote:
> 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. > Actually, the "Execute permission set: was actually for files that had not changed. I did "fossil ci -m 'comment'". I should probably always specify which files to commit, but sometimes when "fossil changes" shows what I intend to commit, I omit the file names, Anyway, there more files than expected in the check-in. > 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. I think "execute permission" is a tag in Fossil. Tags can be set/cleared with the "fossil tag" command, like the "svn propset" command.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
