[Bug 4174] New: Mass addition of execute bit

[mercurial-bugs at selenic.com]

http://bz.selenic.com/show_bug.cgi?id=4174

          Priority: normal
            Bug ID: 4174
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Mass addition of execute bit
          Severity: bug
    Classification: Unclassified
                OS: Mac OS
          Reporter: gregory.szorc at gmail.com
          Hardware: PC
            Status: UNCONFIRMED
           Version: unspecified
         Component: Mercurial
           Product: Mercurial

I'm not 100% confident this is Mercurial's fault, but I was doing my regular
patch workflow with the Firefox source tree and noticed that one of my `hg
amend` managed to update the execute bit on thousands of files.

Mercurial: 2.9+173-0e2877f8605d
mutable-history: 5af309865040

OS X 10.9 with repo living on an HFS+ filesystem. No filesystem modifications
or anything crazy like that.

My workflow:

1) hg pull https://hg.stage.mozaws.net/gecko
2) hg rebase -b gps/build/foo -d central/default
3) hg up gps/build/foo
4) <edit some files>
5) hg amend

After one of those amends was taking a while, I peaked at `hg diff -c .` and
noticed a gazillion of the following:

diff --git a/.gdbinit b/.gdbinit
old mode 100644
new mode 100755

There may have been a merge conflict in the rebase involved in there. I would
have resolved things then executed `hg rebase --continue`.

If I peruse through `hg --hidden log`, the first changeset that picked up the
mode changes was "temporary amend commit for 52c3f897a895." Perhaps that's
related?

It's entirely possible some other process on my machine did the equivalent of a
`chmod -R`. I looked through the hg commit history and didn't see anything
obvious from the past few days that could be to blame. I didn't look too hard
though. I suspect it was the Firefox build system (somehow).

-- 
You are receiving this mail because:
You are on the CC list for the bug.