spurious "exec mode has been unset"

Issue #354 resolved
Mads Kiilerich
created an issue

I have seen some situations where the changeset view reported for a file that "exec mode has been unset". For other files it failed to report the same message when it should.

The changesets are applied mq patches. The output of log -p, diff and export looks fine, but the thg output isn't fully reliable.

Using 2.0.2.

Comments (6)

  1. Mads Kiilerich reporter

    The patches are applied - and I'm surprised too ;-)

    I don't know exactly what to expect, but it seems like strange things happens even without mq: the x bit is not shown when new files are added in a changeset.

    diff --git a/a b/a
    new file mode 100755
    --- /dev/null
    +++ b/a
    @@ -0,0 +1,1 @@
    diff --git a/b b/b
    new file mode 100644
    --- /dev/null
    +++ b/b
    @@ -0,0 +1,1 @@

    Modifying the mode in later changesets also don't show up in thg.

    - but sometimes it reports that "exec mode has been unset" - I don't know when.

  2. Log in to comment