Feature #1149
closed
file size display with Bazaar repositories
Added by Andreas Deininger over 16 years ago.
Updated over 15 years ago.
Description
Currently, the file size is shown as "?" when browsing a Bazaar repository. The attached patch (partly) fixes that issue.
Please note that this patch is far from ideal since:
a) it does not work if the bazaar branch does not have a working tree
b) it only works for the latest revision
c) wrong file sizes may be displayed if the working tree is not up to date with the bazaar branch
A better solution would be to use something like:
$ bzr cat -r 10 /file/in/repo | wc -c
However that does not work on windows platforms.
As workaround, maybe one could execute 'bzr cat -r 10 /file/in/repo' as via IO.popen and determine the byte count in Ruby then.
Files
- Category set to SCM
- Status changed from New to Closed
- Target version set to 0.8
- Resolution set to Fixed
Committed in r1537.
I think bzr cat -r 10 /file/in/repo | wc -c
would be really slow with big/lots of files.
- Status changed from Closed to Reopened
I'm on 0.8.2 stable and bazaar repositories are showing a question mark for filesizes here, even though it was supposedly fixed in 0.8.0 RC1. I'm going to see if it's fixed in 0.8.3 now but I figured this should be reopened.
Joe Kelk wrote:
I'm on 0.8.2 stable and bazaar repositories are showing a question mark for filesizes here, even though it was supposedly fixed in 0.8.0 RC1. I'm going to see if it's fixed in 0.8.3 now but I figured this should be reopened.
EDIT: It's still broken on 0.8.3.
- Status changed from Reopened to Closed
It only works for the latest revision of files in your working tree.
If this doesn't work, please read SubmittingBugs and fill a defect report.
Also available in: Atom
PDF