b7c8bf5274
When annex.thin is set, adding an object will add the execute bits to the work tree file, and this does mean that the annex object file ends up executable. This doesn't add any complexity that wasn't already present, because git annex add of an executable file has always ingested it so that the annex object ends up executable. But, since an annex object file can be executable or not, when populating an unlocked file from one, the executable bit is always added or removed to match the mode of the pointer file. |
||
|---|---|---|
| .. | ||
| patches | ||
| tests | ||
| cabal-wrapper | ||
| changelog | ||
| compat | ||
| control | ||
| copyright | ||
| create-standalone-changelog | ||
| doc-base | ||
| git-annex.lintian-overrides | ||
| NEWS | ||
| rules | ||