summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-08-22 12:17:17 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-08-22 12:17:17 -0400
commitee4e6549b690f91dcf70c152d143faa9e1216726 (patch)
tree3760339cabd7b1b22678710a53e8b41b5c3b2511
parent0768ec19e2484fc7dbc4d0fd6502f7934018ee09 (diff)
reassign bug from git-annex to current world at large
-rw-r--r--doc/bugs/inconsistent_use_of_SI_prefixes.mdwn17
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/bugs/inconsistent_use_of_SI_prefixes.mdwn b/doc/bugs/inconsistent_use_of_SI_prefixes.mdwn
index 97073d174..cf0a2d8f1 100644
--- a/doc/bugs/inconsistent_use_of_SI_prefixes.mdwn
+++ b/doc/bugs/inconsistent_use_of_SI_prefixes.mdwn
@@ -36,3 +36,20 @@ Notice `mebibytes` and `gigabytes`. It is unclear whether those are gigabytes (1
### Please provide any additional information below.
nil.
+
+> git-annex consistently uses the powers of ten units
+> for disk storage sizes. Its "gigabyte" is the SI gigabyte.
+>
+> It uses the absurdly named units for powers of 2 for memory sizes,
+> in the few places it deals with memory (probably only the above bloom
+> filter size number).
+>
+> AFAIK I am complying with all relevant standards and best practices.
+> Even though I consider them rather dumb, as is clear if you
+> [read the opionated source code I wrote to handle this]().
+>
+> If git-annex used "gigabyte", the numbers it reports for disk size
+> would not match the numbers disk vendors and most tools use.
+>
+> [[bug_is_in_world_not_in_git-annex|done]] --[[Joey]]
+