Sorry, forget to tell you that this behavior is shown using Mercurial V1.3.1.

Additionally, I would like to tell you why, at least for us, this bug is
urgent. We develop on Windows but a Linux Server running Hudson checks out
our sources from a Mercurial repository and builds our sources. There are a
lot of Bash-Scripts which are also checked out from our repository. Now ig
we check in a script on Windows we cannot set the 'x' bit (I don't know a
way how to do it, at least). So we 'chmod +x' the Bash scripts and check
them in again. These changes often need to be merged by the developers
working on Windows. However, everytime a merge occurs on Windows all the
x-bits are lost and with their next commit/push to our central repository
the Hudson Server checks out the changes and starts building. However, the
build scripts are not executable anymore and our build fails...

So even if the x-bit issue seems not urgent to most of you it is definitely
a show stopper for us. We can workaround this issue only by making sure all
developers can pull the 'chmod +x' Bash script changes without needing a 'hg
merge'. In other words, everytime a bash script is added and/or chmod'ed we
need to synchronize all developers to a point where they can safely pull.
The advantages of working with a DVCS vanish then...