balanced preferred content and --rebalance
authorJoey Hess <joeyh@joeyh.name>
Fri, 9 Aug 2024 18:16:09 +0000 (14:16 -0400)
committerJoey Hess <joeyh@joeyh.name>
Fri, 9 Aug 2024 18:16:09 +0000 (14:16 -0400)
commit3ce2e95a5f867e09ffeb1f3eaa6990d9f8fc00e7
treea589c66ada43a16190660e5381d87c787c758e8a
parent152c87140b1d08cc9827b3f4faca325c5d814be8
balanced preferred content and --rebalance

This all works fine. But it doesn't check repository sizes yet, and
without repository size checking, once a repository gets full, there
will be no other repository that will want its files.

Use of sha2 seems unncessary, probably alder2 or md5 or crc would have
been enough. Possibly just summing up the bytes of the key mod the number
of repositories would have sufficed. But sha2 is there, and probably
hardware accellerated. I doubt very much there is any security benefit
to using it though. If someone wants to construct a key that will be
balanced onto a given repository, sha2 is certianly not going to stop
them.
Annex.hs
Annex/FileMatcher.hs
CHANGELOG
CmdLine/GitAnnex/Options.hs
Limit.hs
Utility/Hash.hs
doc/design/balanced_preferred_content.mdwn
doc/git-annex-common-options.mdwn
doc/git-annex-preferred-content.mdwn
doc/preferred_content.mdwn
doc/todo/git-annex_proxies.mdwn