If I remove the mtn:execute flag on a file, on an unrelated "mtn revert"
I still get "mtn: reverting mtn:execute" outputs. The file permissions
are set correctly, but the output is confusing, I think. Once a "mtn
attr drop" was done on an attribute I would have expected that "mtn
revert" no longer tells me about it.
Here is a simple test which shows the confusing output:
--------------------------------------------------------------
$ mkdir /tmp/test
$ cd /tmp/test
$ mtn --db=/tmp/test.db db init
$ mtn --db=/tmp/test.db setup -b test
$ echo foo > foo.txt
$ mtn add foo.txt
mtn: adding foo.txt to workspace manifest
$ mtn attr set foo.txt mtn:execute true
$ mtn stat
Current branch: test
Changes against parent
added ""
added foo.txt
attr on foo.txt
attr mtn:execute
value true
$ mtn ci -m "1"
mtn: beginning commit on branch 'test'
mtn: committed revision 70db0f4e4d1ddd39e529af65796c3a46c481356e
$ mtn revert foo.txt
mtn: reverting mtn:execute on foo.txt
$ ls -l foo.txt
-rwxr-xr-x 1 rse wheel 4 Apr 11 12:24 foo.txt
$ mtn attr drop foo.txt mtn:execute
$ mtn stat
Current branch: test
Changes against parent 70db0f4e4d1ddd39e529af65796c3a46c481356e
unset on foo.txt
attr mtn:execute
$ mtn ci -m "2"
mtn: beginning commit on branch 'test'
mtn: committed revision a9f777b693d86640cfbaf4ec6c19a8daa49cc79d
$ ls -l foo.txt
-rw-r--r-- 1 rse wheel 4 Apr 11 12:24 foo.txt
$ mtn revert foo.txt
mtn: reverting mtn:execute on foo.txt
$ mtn attr get foo.txt mtn:execute
No attribute 'mtn:execute' on path 'foo.txt'
$ mtn revert foo.txt
mtn: reverting mtn:execute on foo.txt
--------------------------------------------------------------
It is just a bug in the output or do I miss something here?
Ralf S. Engelschall
[email protected]
www.engelschall.com
_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel
