https://bz.mercurial-scm.org/show_bug.cgi?id=6973
Bug ID: 6973
Summary: Bogus "exec mode has been unset" for files that never
had it to begin with
Product: Mercurial
Version: 7.0.2
Hardware: PC
OS: Linux
Status: UNCONFIRMED
Severity: bug
Priority: wish
Component: Mercurial
Assignee: bugzi...@mercurial-scm.org
Reporter: php4...@gmail.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---
I'm using TortoiseHg as a GUI; I don't know how to test for this issue with hg
alone, but I'm pretty sure the issue is in hg and has nothing to do with
TortoiseHg.
On Linux, I have a folder that is a hg repository.
>From that folder, I ran:
```
rsync -tpvz --exclude='.gitignore' "r...@example.com:/path/to/folder/*" ./
```
which resulted in overwriting some of the files with those downloaded by rsync.
Most of the files weren't even toucned by rsync.
Then I opened the repository in TortoiseHg and looked at the status of the
working directory.
EVERY SINGLE FILE is listed as modified, and the diff view shows no changes at
all, but has this note at the top:
```
exec mode has been unset
```
but most of these are files that never had exec mode to begin with.
For context, these files I downloaded with rsync were the files in my repo that
I first uploaded to a server, then downloaded on a Windows machine, then
reuploaded from there, and then downloaded again on my original Linux machine.
I don't care what might have happened to the permissions of the files when
rsyncing them back and forth through a windows machine (I might have done
something wrong using rsync), but it is **physically impossible** that the
current status of a file in the working directory is "exec mode has been unset"
when the file didn't have exec mode in the previous commit (or ever).
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
