mirror of
https://github.com/facebook/sapling.git
synced 2024-10-09 08:18:15 +03:00
2aaabbf1cc
Previous to this, 'commit -A' would add as normal files, files that were already committed as largefiles, resulting in files being listed twice by 'status -A'. It also missed when (only) a largefile was deleted, even though status reported it as '!'. This also has the side effect of properly reporting the state of the affected largefiles in the post commit hook after a remove that also affected a normal file (the largefiles used to be 'R', now are properly absent). Since scmutil.addremove() is called both by the ui command (after some trivial argument validation) and during the commit process when -A is specified, it seems like a more appropriate method to wrap than the addremove command. Currently, a repo is only enabled to use largefiles after an add that explicitly identifies some file as large, and a subsequent commit. Therefore, this patch only changes behavior after such a largefile enabling commit. Note that in the test, if the final commit had a '-v', 'removing large8' would be printed twice. Both of these originate in removelargefiles(). The first print is in verbose mode after traversing remove + forget, the second is because the '_isaddremove' attr is set and 'after' is not. |
||
|---|---|---|
| .. | ||
| convert | ||
| highlight | ||
| inotify | ||
| largefiles | ||
| zeroconf | ||
| __init__.py | ||
| acl.py | ||
| bugzilla.py | ||
| children.py | ||
| churn.py | ||
| color.py | ||
| eol.py | ||
| extdiff.py | ||
| factotum.py | ||
| fetch.py | ||
| gpg.py | ||
| graphlog.py | ||
| hgcia.py | ||
| hgk.py | ||
| histedit.py | ||
| interhg.py | ||
| keyword.py | ||
| mq.py | ||
| notify.py | ||
| pager.py | ||
| patchbomb.py | ||
| progress.py | ||
| purge.py | ||
| rebase.py | ||
| record.py | ||
| relink.py | ||
| schemes.py | ||
| share.py | ||
| transplant.py | ||
| win32mbcs.py | ||
| win32text.py | ||