status: More accurate display of sizes of tmp and bad keys.
Can't trust the key size to be accurate for tmp and bad keys, so check actual file size. In the wild I saw the old code be wrong by a factor of about 100! If all tmp/bad keys are empty, they're not shown in status at all. Showing 0 bytes and suggesting to clean it up seemed weird..
This commit is contained in:
parent
83bbb3bc93
commit
89ee70c43a
2 changed files with 14 additions and 6 deletions
1
debian/changelog
vendored
1
debian/changelog
vendored
|
@ -7,6 +7,7 @@ git-annex (3.20120310) UNRELEASED; urgency=low
|
|||
space, but now only needs to store the set of file contents that
|
||||
are present in the annex in memory.
|
||||
* status: Fixed to run in constant space.
|
||||
* status: More accurate display of sizes of tmp and bad keys.
|
||||
|
||||
-- Joey Hess <joeyh@debian.org> Sat, 10 Mar 2012 14:03:22 -0400
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue