On Sun, Apr 5, 2009 at 10:10 PM, Derek Scherger
<address@hidden> wrote:
On Wed, Apr 1, 2009 at 9:06 AM, Jack Lloyd
<address@hidden> wrote:
I just noticed that in 0.43 the revert command has gotten quite noisy,
and reports reverting of mtn:execute and mtn:manual_merge metadata,
even if no actual reversion took place:
This is probably due to the changes I made to revert leading up to 0.43 to make it revert attributes more carefully. I haven't had a chance to look into it yet but I will in the next few days.
I finally had a minute to look into this and it is due to the changes I made to revert to do something more sensible with attributes. It's a trivial fix to change a P(F(... into an L(FL(... to silence this but I wonder if that's a bit too silent. i.e. do we never want to hear about attributes being changed?
Alternatively, what if we made the code that mucks with the execute bits print something when it actually makes a change? i.e. when called to set or clear the x bits only say something when they are actually being changed and otherwise be silent. This would affect revert and any other workspace modifying commands and might still be annoying but it might also be useful information.