On Sat, Apr 11, 2009, Ralf S. Engelschall wrote:
> 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:
> [...]
> 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?
This is with Monotone 0.43, BTW. And, sorry, I see in my mail backlog
that this seems to be already reported under subject "0.43's revert is
noisy: 'mtn: reverting mtn:execute on ...'", too. Seems like exactly the
same problem.
Ralf S. Engelschall
[email protected]
www.engelschall.com
_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel
