2743224658
v6: When a file is unlocked but has not been modified, and the unlocking is only staged, git-annex add did not lock it. Now it will, for consistency with how modified files are handled and with v5. Note the removal of the sameInodeCache check. Otherwise it would see that the unmodified file is unmodified and stop there. That check seems to have been copied from the direct mode branch. But, direct mode had a specific reason to check for unmodified content, that does not apply to v6. The second pass means there is potential for a race, eg the unlocked file could be modified in between the first and second passes. No problem with that, since both passes do the same thing. This commit was sponsored by Jake Vosloo on Patreon. |
||
|---|---|---|
| .. | ||
| GitAnnex | ||
| GitAnnexShell | ||
| Action.hs | ||
| Batch.hs | ||
| GitAnnex.hs | ||
| GitAnnexShell.hs | ||
| GitRemoteTorAnnex.hs | ||
| GlobalSetter.hs | ||
| Option.hs | ||
| Seek.hs | ||
| Usage.hs | ||