Matt Harbison b617460d47 largefiles: fix a traceback when addremove follows a remove (issue3507) ... The problem only occurred if a file was removed with 'hg rm' (as opposed to the OS utilities), and then addremove was run before a commit. Both normal and large files were affected. Ensuring that the file exists prior to an lstat() for size seems like the Right Thing. But oddly enough, the missing file that was causing lstat() to blow up was a standin when a largefile was removed, which seems fishy, because a standin should never be added as a largefile. I was then able to get a standin added as a largefile (whose name is 'large') with hg addremove --config largefiles.patterns=**large which also causes a backtrace. That will be fixed next.		2012-07-19 11:12:05 -04:00
..
__init__.py	largefiles: clarify help when options are ignored until first add is done	2011-12-28 00:01:48 +01:00
basestore.py	largefiles: batch statlfile requests when pushing a largefiles repo (issue3386)	2012-06-24 20:36:22 +02:00
CONTRIBUTORS	hgext: add largefiles extension	2011-09-24 17:35:45 +02:00
lfcommands.py	largefiles: optimize status by synchronizing lfdirstate with the largefile on update	2012-07-13 14:49:16 +02:00
lfutil.py	largefiles: lowercase messages	2012-06-12 14:18:18 +02:00
localstore.py	peer: introduce peer methods to prepare for peer classes	2012-07-13 21:46:53 +02:00
overrides.py	largefiles: fix a traceback when addremove follows a remove (issue3507)	2012-07-19 11:12:05 -04:00
proto.py	peer: introduce real peer classes	2012-07-13 21:47:06 +02:00
remotestore.py	largefiles: batch statlfile requests when pushing a largefiles repo (issue3386)	2012-06-24 20:36:22 +02:00
reposetup.py	largefiles: defer lfdirstate.drop() until after commit (issue3364)	2012-07-19 10:00:15 -04:00
uisetup.py	peer: introduce real peer classes	2012-07-13 21:47:06 +02:00
wirestore.py	largefiles: batch statlfile requests when pushing a largefiles repo (issue3386)	2012-06-24 20:36:22 +02:00